System and Method for Virtualized Functions in Control and Data Planes

ABSTRACT

Systems and methods for operating network slices in a communication network such as a 5 th  generation wireless communication network are provided. Mobile device attach requests can be handled in which an appropriate network slice is selected for attaching the mobile device to. Customer service requests can be handled using existing network slices or by instantiating new network slices as needed. Mobile devices can be associated to new network slices due to roaming. Network slices can be monitored and scaled as required to maintain performance. Cloud resource assignment, mobile device power management, traffic engineering and flow management operations are also disclosed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Application No. 62/169,243,filed Jun. 1, 2015, U.S. 62/220,564, filed Sep. 18, 2015, and U.S.62/220,643, filed Sep. 18, 2015. The content of the above applicationsare incorporated by reference in their entirety.

FIELD OF THE INVENTION

The present invention pertains to the field of communication networksand in particular to a system and method for providing virtualizedfunctions in control and data planes, and for operating a communicationnetwork having network slices.

BACKGROUND

Using technologies, such as Network Function Virtualization (NFV),Network Slicing and Software Defined Networking (SDN), communicationsnetworks can be managed so that different subnetworks can be created,each of which is tailored to address demands from different customers.Network slicing allows an underlying resource pool to be segmented intoprivate networks which are isolated from each other in terms of trafficand resource usage. The underlying resources, including connectivityresources and processing and storage resources, can be partitionedamongst a number of different networks. By allowing for traffic andresource isolation between networks, the slices can be sufficientlyisolated that, to any entity within a slice, the slice itself is acomplete network. By using NFV and other virtualization techniques,network functions can be placed throughout the network, and logicalconnections between the virtual entities can be defined. Changing ormodifying the resources allocated to network functions or links betweenfunctions can be done dynamically to allow for a dynamic topology tosuit the needs of the network. These flexible network architectures areof interest in mobile networks, both in the core and possibly in theRadio Access Network, and are being studied as candidates for use innext generation mobile networks, such as so-called fifth generation (5G)networks. However, managing variable and competing demands on apotentially large network scale is a complex proposition requiring aneffective architecture and management thereof.

Therefore there is a need for a system and method for operating acommunication network having network slices, that obviates or mitigatesone or more limitations of the prior art.

This background information is provided to reveal information believedby the applicant to be of possible relevance to the present invention.No admission is necessarily intended, nor should be construed, that anyof the preceding information constitutes prior art against the presentinvention.

SUMMARY

An object of embodiments of the present invention is to provide a systemand method for providing virtualized functions in control and dataplanes, and for operating a communication network having network slices.In accordance with embodiments of the present invention, there isprovided a method for managing a mobile device attach request in acommunication network having a plurality of network slices. The methodincludes instantiating a global connection and mobility management(G-CMM) function in the communication network, the G-CMM functionconfigured to operate across the plurality of network slices. The methodincludes selecting an appropriate network slice from the plurality ofnetwork slices with the G-CMM function. The method includes attachingthe mobile device to the appropriate network slice. Optionally, thecommunication network comprises an access node, the mobile device isassociated with the access node, and the G-CMM function determines andattaches the mobile device to the appropriate network slice usingextended capabilities of the access node.

In accordance with embodiments of the present invention, there isprovided a method for managing a request, such as a customer servicerequest, in a communication network. The method includes instantiating aglobal connection and mobility management (G-CMM) function in thecommunication network. The method includes receiving the request by theG-CMM function. The method includes determining if the request can beaccommodated using one of a plurality of pre-existing network slice ofthe communication network. The method includes instantiating a newnetwork slice to accommodate the request when the request cannot beaccommodated using any of the plurality of pre-existing network slices.

In accordance with embodiments of the present invention, there isprovided a method for managing a mobile device roaming between a firstcoverage area associated with a first network slice and a secondcoverage area associated with a second network slice. The methodincludes associating the mobile device with the first network slice whenthe mobile device is in the first coverage area. The method includesassociating the mobile device with the second network slice when themobile device is in the second coverage area.

In accordance with embodiments of the present invention, there isprovided method for managing a mobile device associated with a firstnetwork slice in a communication network. The method includesinstantiating a global connection and mobility management (G-CMM)function in the first network slice. The method includes determining ifthe mobile device is in a coverage area of the first network slice withthe G-CMM function. The method includes assigning the mobile device to asecond network slice when the mobile device is outside of the coveragearea of the first network slice.

In accordance with embodiments of the present invention, there isprovided a method for managing one or more network slices in acommunication network. The method includes instantiating a connectionand mobility management (CMM) function within at least one networkslice. The method includes measuring one or more performance metricsindicative of performance of the one or more network slices using theCMM function. The method includes scaling the one or more network slicesbased on the measured one or more performance metrics.

In accordance with embodiments of the present invention, there isprovided a method for managing mobile device connections in acommunication network. The method includes providing a network slicebelonging to the communication network. The method includes attaching amobile device to the network slice. The method includes instantiating aconnection management (CM) function in the network slice. The methodincludes determining a cloud candidate set for the mobile device usingthe CM function. The method includes communicatively coupling the mobiledevice to the cloud candidate set.

In accordance with embodiments of the present invention, there isprovided a power savings method for a mobile device communicativelycoupled to a communication network. The method includes providing anetwork slice belonging to the communication network. The methodincludes attaching the mobile device to the network slice. The methodincludes instantiating a connection management (CM) function in thenetwork slice. The method includes determining power savings operatingparameters for the mobile device using the CM function. The methodincludes operating the mobile device according to the power savingsoperating parameters.

In accordance with embodiments of the present invention, there isprovided a method for transmitting packets between a source node and adestination node in a communication network. The method includesassociating a network slice with the source node. The method includesinstantiating a flow management (FM) function in the network slice. Themethod includes instantiating a traffic engineering (TE) function in thecommunication network. The method includes performing, using the TEfunction, path computations to determine paths and capacity bounds forlinks between the source node and destination node for the networkslice. The method includes splitting flows along the determined pathsusing the FM function. The method includes transmitting packets betweenthe source node and the destination node along the determined paths. Themethod includes causing, using the FM function, the determined capacitybounds to be respected.

In accordance with embodiments of the present invention, there isprovided a method for transmitting packets between a source node and adestination node in a communication network, the source node beingassociated with a network slice. The method includes instantiating atraffic engineering (TE) function in the communication network. Themethod includes performing, using the TE function, path computations todetermine paths and capacity bounds for links between the source nodeand destination node for the network slice. The method includes routingpackets between the source node and the destination node via thedetermined paths. The method includes causing, using the IL function,the determined capacity bounds to be respected.

In accordance with embodiments of the present invention, there isprovided a connection management apparatus in a communication networkhaving a plurality of network slices. The apparatus comprises amicroprocessor operatively coupled to a network interface. The apparatusis configured, in response to an attach request from a mobile device toselect a network slice from a plurality of network slices. The apparatusis further configured to transmit instructions, via the networkinterface to at least one node of the communication network, to attachthe mobile device to the network slice.

In accordance with embodiments of the present invention, there isprovided a connection management apparatus in a communication networkhaving a plurality of network slices. The apparatus is configured, inresponse to a request to determine if the request can be accommodatedusing one of a plurality of pre-existing network slice of thecommunication network. The apparatus is further configured toinstantiate a new network slice to accommodate the request when therequest cannot be accommodated using any of the plurality ofpre-existing network slices.

In accordance with embodiments of the present invention, there isprovided an apparatus for managing a mobile device roaming between afirst coverage area associated with a first network slice and a secondcoverage area associated with a second network slice. The apparatus isconfigured to associate the mobile device with the first network slicewhen the mobile device is in the first coverage area. The apparatus isfurther configured to associate the mobile device with the secondnetwork slice when the mobile device is in the second coverage area.

In accordance with embodiments of the present invention, there isprovided an apparatus for managing a mobile device associated with afirst network slice in a communication network. The apparatus isconfigured to determine if the mobile device is in a coverage area of afirst network slice. The apparatus is further configured to assign themobile device to a second network slice when the mobile device isoutside of the coverage area of the first network slice. The apparatusis instantiated in the first network slice as a global connection andmobility manager (G-CMM).

In accordance with embodiments of the present invention, there isprovided an apparatus for managing one or more network slices in acommunication network. The apparatus is configured to measure one ormore performance metrics indicative of performance of the one or morenetwork slice. The apparatus is further configured to scale the one ormore network slices based on the measured one or more performancemetrics. Measuring of the one or more performance metrics is performedby a connection and mobility manager portion of the apparatusinstantiated in at least one of the one or more network slices.

In accordance with embodiments of the present invention, there isprovided an apparatus for managing mobile device connections in acommunication network. The apparatus is configured to provide a networkslice belonging to the communication network. The apparatus is furtherconfigured to attach a mobile device to the network slice. The apparatusis further configured to instantiate a connection management (CM)function in the network slice. The apparatus is further configured todetermine a cloud candidate set for the mobile device using the CMfunction. The apparatus is further configured to communicatively couplethe mobile device to the cloud candidate set.

In accordance with embodiments of the present invention, there isprovided an apparatus for managing a mobile device communicativelycoupled to a communication network. The apparatus is configured toprovide a network slice belonging to the communication network. Theapparatus is further configured to attach the mobile device to thenetwork slice. The apparatus is further configured to instantiate aconnection management (CM) function in the network slice. The apparatusis further configured to determine power savings operating parametersfor the mobile device using the CM function. The apparatus is furtherconfigured to operate the mobile device according to the power savingsoperating parameters.

In accordance with embodiments of the present invention, there isprovided a system for controlling transmission of packets between asource node and a destination node in a communication network, thesource node associated with a network slice. The system includes atraffic engineering (TE) manager in the communication network, the TEmanager configured to perform path computations to determine paths andcapacity bounds for links between the source node and destination nodefor the network slice. The system further includes a flow manager (FM)located in the network slice, the FM comprising a second microprocessoroperatively coupled to a second network interface and configured tosplit flows along the determined paths and to cause the determinedcapacity bounds to be respected. Packets are transmitted between thesource node and the destination node along the determined paths. The TEmanager and the FM include microprocessors operatively coupled tonetwork interfaces.

In accordance with embodiments of the present invention, there isprovided a traffic engineering (TE) manager for controlling transmissionof packets between a source node and a destination node in acommunication network, the source node associated with a network slice.The TE manager is configured to perform path computations to determinepaths and capacity bounds for links between the source node anddestination node for the network slice. The TE manager is furtherconfigured to cause packets to be routed between the source node and thedestination node via the determined paths. The TE manager is furtherconfigured to cause the determined capacity bounds to be respected.

BRIEF DESCRIPTION OF THE FIGURES

Further features and advantages of the present invention will becomeapparent from the following detailed description, taken in combinationwith the appended drawings, in which:

FIG. 1 illustrates operations according to a method and apparatus forproviding network connection management, in accordance with embodimentsof the present invention.

FIG. 2A illustrates network slice association within the managementplane, in accordance with some embodiments of the present invention.

FIG. 2B illustrates network slice association at the edge of thenetwork, in accordance with other embodiments of the present invention.

FIG. 3 illustrates a procedure for connecting a device to a networkslice, in accordance with some embodiments of the present invention.

FIG. 4 illustrates a procedure for connecting a device to a networkslice, in accordance with some embodiments of the present invention.

FIG. 5 illustrates a network slice association procedure, according toan embodiment of the present invention.

FIG. 6 illustrates a network slice association procedure, according toanother embodiment of the present invention.

FIG. 7 illustrates signaling flow associated with an attach request, inaccordance with some embodiments of the present invention.

FIG. 8A illustrates an overview of the communication networkarchitecture in accordance with embodiments of the present invention.

FIG. 8B illustrates an overview of the communication networkarchitecture in accordance with embodiments of the present invention.

FIG. 8C illustrates an overview of the communication networkarchitecture in accordance with embodiments of the present invention.

FIG. 9 illustrates a network slice, according to an embodiment of thepresent invention.

FIG. 10 illustrates a network slice instantiation procedure, accordingto an embodiment of the present invention.

FIG. 11 illustrates network slice instantiation, according to anotherembodiment of the present invention.

FIG. 12 illustrates multiple network slice types based on included typesof functions, according to embodiments of the present invention.

FIG. 13 illustrates a plurality of network slices and a management planeused for network slice management, in accordance with embodiments of thepresent invention.

FIG. 14A illustrates a network slicing configuration includinginstantiation of CM and CSM management plane functions in accordancewith an embodiment of the present invention.

FIG. 14B illustrates a network slicing configuration includinginstantiation of connection management functions, in accordance with anembodiment of the present invention.

FIG. 14C illustrates a network slicing configuration includinginstantiation of customer service management functions, in accordancewith an embodiment of the present invention.

FIG. 15 illustrates a method for managing infrastructure in acommunication network supporting a plurality of network slices andsupported by a plurality of network operators and/or infrastructureproviders, in accordance with an embodiment of the present invention.

FIG. 16 illustrates a network configuration illustrative ofinfrastructure management in accordance with some embodiments of thepresent invention.

FIG. 17 also illustrates a network configuration illustrative ofinfrastructure management in accordance with some embodiments of thepresent invention.

FIG. 18 illustrates configuration of the v-s-IM, as configured tonegotiate with the spectrum broker, and the relationship of the v-s-IMwith other functions, in accordance with an embodiment of the presentinvention.

FIG. 19 illustrates a spectrum negotiator function in relation withother functions, in accordance with another embodiment of the presentinvention.

FIG. 20 illustrates end-to-end service management using Software DefinedNetworking (SDN), in accordance with embodiments of the presentinvention.

FIG. 21 illustrates a method for end-to-end service management in anSDN-capable communication network supporting a plurality of networkslices, in accordance with embodiments of the present invention.

FIG. 22 illustrates an apparatus provided in accordance with embodimentsof the present invention.

It will be noted that throughout the appended drawings, like featuresare identified by like reference numerals.

DETAILED DESCRIPTION

As used herein, a “network” or “communication network” may servicevarious devices including but not necessarily limited to mobile devices.Such a network may include a radio access portion and backhaul portion.The network may further comprise various virtualized components as willbecome readily apparent herein. A primary example of such a network is a5^(th) generation mobile network, for example as defined by the NextGeneration Mobile Networks Alliance, which is reconfigurable and capableof operating according to network slicing, as described below.

Network operations can be categorized into management plane, controlplane and data plane operations. The control plane performs operationssuch as network device configuration, while the data plane handles datapackets by the network devices as configured via the control plane. Themanagement plane may be considered to be part of the control plane, andis usable for example for network administration and to manageconfiguration of the control plane, for example by enabling operators tointeract with the network.

As used herein, the term “User Equipment” (UE) is used for purposes ofclarity. However, the UE may refer to one of a variety of devices, suchas mobile devices, stationary or mobile machine-type devices, or thelike, which communicate with an access node via wireless communication.One skilled in the art will appreciate that a mobile device is a devicedesigned to connect to a mobile network. This connection typically makesuse of a wireless connection to an access node. Although the mobilenetwork is designed to support mobility, it is not necessary that themobile device itself be mobile. Some mobile devices, such as meteringdevices (e.g. smart meters) may not be capable of mobility, but stillmake use of the mobile network.

Network slicing refers to a technique for separating different types ofnetwork traffic which can be used in reconfigurable networkarchitectures, such as networks employing network functionvirtualization (NFV). A network slice (as defined in 3GPP TR 22.891entitled “Study on New Services and Markets Technology Enablers,”Release 14, Version 1.2.0, Jan. 20, 2016), is composed of a collectionof logical network functions that supports the communication servicerequirements of particular use cases. One use of network slicing is inthe core network. Through the use of network slicing, different serviceproviders can have distinct core networks that run on the same physicalset of network and computing resources. This can also be used to createa virtual network dedicated to particular types of network traffic. Itshould be understood that this discussion is not intended to exclude theapplication of network slicing as it applies to the radio access edge ofthe Radio Access Network (RAN), which may need specific functionality tosupport multiple network slices or partitioning of resources fordifferent network slices. In order to provide performance guarantees,the network slices can be isolated from each other so that one slicedoes not negatively affect the other slices. The isolation is notrestricted to different types of services, but also allows the operatorto deploy multiple instances of the same network partition.

In contrast with having all mobile devices connect with the networkthrough a mobility management Entity (MME) determined by a networkinfrastructure component (e.g. base station, access point, eNB), networkslicing allows the instantiation of separate network slices respectivelydirected toward different network services. This allows for separationof different types of traffic, the different types of trafficpotentially having different packet processing requirements and QoSrequirements. Network slicing may correspond to the allocation of pooledresources to offer different services to different customers or groupsof customers, such that different services are supported by differentcustomized virtual networks, where the different customized virtualnetworks are substantially separate from one another from the customer'spoint of view. The pooled resources may be commercial-off-the-shelfhardware components capable of configuration through virtualizationapproaches, such as NFV, in order to support various networkfunctionalities for supporting the operations of the network slices.

According to embodiments of the present invention, the communicationnetwork architecture is based on the use of virtualized network elementsand links. This can be realised through the use of a network functionvirtualization (NFV) framework, along with software defined resourceallocation. The NFV framework can be used to define a plurality ofvirtual network functions (VNFs), each of which can correspond to afunction enabling operation of a communication network. For example aVNF can provide the functions of a router, switch, gateway, firewall,load balancer, server and the like. The function is virtualized in thesense that although it is instantiated upon physical resources, thefunction purely resides within the network. In a virtualized domain,there is reduced or no need for certain physical nodes, such asgateways. Rather, a computing platform can be employed to instantiatethe function of the physical nodes, such as virtual gateway functions.These functions use virtual resources, such as computing, storage andnetworking resources. This provides an alternative to utilizingdedicated hardware resources. To other entities in the network, thevirtualized entity appears indistinguishable from a real entity. Assuch, VNFs may be instantiated on an as-needed basis using availableresources, both real and virtual. NFV and virtual network functionsarchitecture is described in ETSI GS NFV 001 entitled “network functionvirtualization (NFV); Use Cases”, October 2013 and ETSI GS NFV 002entitled “network function virtualization (NFV); ArchitecturalFramework”, October 2013, for example.

A NFV management and orchestration (MANO) entity may be used toinstantiate the necessary functional network components to ensure thatthe services identified by a network service (NS) request can be served.The instantiation of a network function (to handle a network servicerequest) can be described by a virtual network function forwarding graph(VNFFG) which defines the set of network functions that are required toprovide the requested service. The VNFFG contains a network forwardingpath (NFP) that defines a sequence of actions that are to be performed,for example by a collection of VNFs, to provide the requested service.

To provide context to aid in the understanding of network slicing, andthe concept of a network slice, it is helpful to understand that inheterogeneous networks in addition to a plurality of different types ofnodes covering different locations, different infrastructure providersmay own different parts of what is considered as an access network (oreven parts of a core network). A Telecommunications Service Provider(TCSP) also referred to as a network operator (NO) or service provider(SP), provides network services to Virtual Network Operators (VNOs).Some examples of these VNOs include an M2M Service Provider (M2M SP), aMobile Virtual Network Operator (MVNO) or another virtual serviceprovider. These VNOs obtain network services, in the form of a networkhaving virtual functions and connections to allow the VNO to provideservice to customers. The TCSP can create the required virtual networkas a network slice from its pool of network resources. The M2M SP has aVN composed of nodes and links, which are typically arranged to form atopology having characteristics specified by the M2M SP. However, the VNresources (both nodes and links) need to be mapped to physicalinfrastructure. The VN may only use a subset of the physical nodes, andeach physical node that the VN uses may not be fully used by that VN. Itshould also be understood that the M2M SP may make use of more than oneTCSP, allowing it to create a network slice spanning across differentnetworks, effectively having a network slice that is a superset of theresources of a single TCSP (or as the case may be, a network slicecomposed of the combination of subsets of the resources of a pluralityof TCSPs). If certain bandwidth requirements are set for each logicallink, then percentages of physical links are allocated to create thevirtual link. This may also include aggregating physical links to createa logical link that may have a greater capacity than a single physicallink. Network slices are the collection of the allocation of theresources in what may be different networks. A network slice, from theperspective of an infrastructure provider may only include resources inthe infrastructure provider network. From the perspective of the M2M SP,the network slice is a substantially seamless aggregation of all networkslices that the M2M SP uses which is analogous to the VN. The TCSP dealswith seamlessly connecting the different network slices ofinfrastructure provider resources, along with network slices from theTCSP resources, to create the M2M VN. It should be understood that atvarious points in time, the total allocation of network slices fordifferent resources may not add up to 100%. If the value is less than100% it means that the resource is not fully utilized. If it exceeds100% it may be a network design choice knowing that there is a very lowlikelihood that all customers will be using a resource at the same time.It should be understood that the size and nature of different networkslices can vary with time as new resources come online or as existingresources are re-allocated. The M2M SP may typically be unaware of thechanges in the infrastructure.

A portion of communication network resources may be allocated for use bya network slice. These resources can include radio access communicationresources, node-to-node communication resources, computationalresources, and memory resources. Resources may further include networkinfrastructure resources such as management plane resources, controlplane resources, and data plane resources. Resources may includehardware resources, such as portions of computer processingcapabilities, or communication resources, such as portions ofcommunication links partitioned by time, frequency, spreading code, or acombination thereof. Nodes in the same network slice may be connected bylogical connections, much as physical nodes in a physical network areconnected by physical connections.

Network Slice Association

Embodiments of the present invention provide for network sliceassociation in a communication network, for associating a mobile device(UE) with one of several network slices supported by the communicationnetwork. A connection manager is configured to determine an associationbetween the UE and one of the network slices. The connection manager maybe located in a management plane separate from the several networkslices, such as in a connection management plane. The connection managermay be instantiated using one or more NFV-enabled nodes in the network,or more generally using computing devices in the network. In someembodiments, the connection manager is instantiated at one or morelocations corresponding to an edge of the network. The connectionmanager may be referred to as a global connection manager to distinguishit from service-specific local connection managers. The globalconnection manager is used to make the association with the networkslice, while the service-specific local connection managers eachcorrespond to a specific network slice and handle connection operationsfor that network slice.

Network slice association includes handling, by at least the connectionmanager, a connection request or network attachment request by a mobiledevice. Having reference to FIG. 1, the operations of the connectionmanager include receiving 110 an indication that the mobile device is tobe associated with the communication network. The indication may be anattach request transmitted by the mobile device, which is transmitteddirectly or indirectly from the mobile device to the connection manager.The operations may further include determining 120 a network slice, outof the plurality of network slices, to which the mobile device is to beassociated. The operations further include transmitting 130 instructionsto at least one node of the communication network and/or executing saidinstructions at least partially by the connection manager. Theinstructions, when carried out, cause the mobile device to be associatedwith the network slice.

In some embodiments, the connection manager is instantiated in amanagement plane, for example in a set of global functions residing in acore of the communication network. In some embodiments, the connectionmanager is instantiated at one or more locations corresponding to anedge of the network, such as an access node to which the mobile devicecommunicates. In some embodiments, the connection manager may beinstantiated at multiple locations, such as multiple access nodes. Adistributed connection manager may be used to handle connection requestsreceived through multiple access nodes. The connection manager may bereferred to as a global connection manager such as a global connectionand mobility manager (G-CMM). The connection manager may also bereferred to as a connection management function.

FIG. 2A illustrates network slice association occurring within amanagement plane 225, in accordance with some embodiments of the presentinvention. The management plane 225 may be a network slice holdingvarious global functions for managing various network slices. In thepresent embodiment, the network slice association operation is made bythe management plane (MP) connection management (CM) function 220. TheCM function may be a separate VNF instantiated at a potentiallyarbitrary location within the network infrastructure separate from theaccess nodes 215. Further, the CM function can be instantiated inmultiple locations within the network. As illustrated in FIG. 2A,example network slices include one or more Mobile Broadband (MBB) slices230, one or more Machine Type Communication (MTC) slices 235, and one ormore critical Machine Type Communication (MTC) slices 240. A UE 205transmits an attach request 210 to an access node 215 of the network.The attach request is forwarded to the CM function 220.

FIG. 2B illustrates network slice association operations performed by aCM instantiated at the edge of the network, in accordance with someembodiments of the present invention. The edge of the network includesan access node 215, for example, and the network slice associationoperation is performed by a CM function 220, which is co-located withthe access node 215. A UE 205 transmits an attach request 210 to theaccess node 215 of the network. The attach request may be containedwithin a Non Access Stratum (NAS) message transmitted by the UE. Theattach request is handled by the CM function 220.

In some embodiments, the CM function can be located at some or all basestations or access point-type entities in the communication networkwhich communicate directly with mobile devices via wirelesscommunication. These entities may be eNBs, and/or Baseband Units (BBUs)in a Cloud Radio Access Network (C-RAN) configuration. Alternatively,the CM function may be located at another entity that is associated witha base station or access point-type entity. A CM function at multiplelocations may be replicated in its entirety at each location orinstantiated in a distributed manner across the locations.

In various embodiments, the instructions transmitted by the connectionmanager include an indication that the mobile device is to be associatedwith a specified network slice out of a plurality of network slices. Theindication may be provided by forwarding an attach request initiallytransmitted by the mobile device, possibly by encapsulating the attachrequest in another control message. The attach request is forwarded to alocal or service-specific connection manager corresponding to thespecified network slice.

In some embodiments, the indication that the mobile device is to beassociated with the communication network includes an identifierindicative of, or correlated with, a particular network slice. Uponreceipt of the indication, the connection manager determines theparticular network slice based on the identifier. As such, the selectionof the network slice may be explicitly or implicitly defined within theindication. The mobile device may therefore explicitly requestassociation with a particular network slice. For example, the mobiledevice may transmit an attach request including a network sliceidentifier which specifically indicates the network slice to which themobile device is to be associated. As another example, the mobile devicemay transmit an attach request including a mobile device identifierwhich is correlated, via a pre-arranged correspondence stored in alookup table, to a particular network slice to which the mobile deviceis to be associated.

Associating a network slice with the mobile device can includemanagement and control plane operations, for example performed by theservice-specific connection manager. For example, association mayinclude authenticating the mobile device, authenticating a network sliceto the mobile device, confirming an authorization of the mobile device,admitting the mobile device to a network slice, establishing signalingand data bearers for the mobile device, establishing network forwardingrules supporting the mobile device, and transmitting an attach responseto the mobile device indicating that association has been performed.

A network slice in an association operation may be newly instantiated,currently in the process of being instantiated, or pre-existing.

In some embodiments, an entity within the network may assign the UE to aparticular network slice. For example, the entity may assign the UE to aparticular network slice when the UE does not request a particularnetwork slice association, or when the requested network sliceassociation is overridden by the entity.

Network slice association may include selecting which network slice, ofa plurality of network slices, is to be associated with a given mobiledevice, and arises in relation to the possibility that a given UE maybelong to one or more instantiated network slices. A slice associationdetermination indicates which network slice the UE is to attach to. Theassociated network slice corresponds to the portion of the communicationnetwork which will carry voice and/or data traffic toward and from themobile device, as well as process said traffic when necessary. Theassociated network slice may provide at least some, or substantiallyall, of the functions and services of the communication network as theyapply to the mobile device. Because different network slices may havedifferent capabilities, network slice association can include selectinga network slice which is capable of satisfying the current communicationrequirements of a mobile device, by having access to an adequate portionof communication network resources.

In some embodiments, particulars of the network slices may be describedby a network service Descriptor (NSD). For example, in some embodiments,the NSD contains a network slice identifier (NS ID), which, oncedetermined for example by obtaining the NS ID from a broadcast channelor by another method, can be included in the header of an uplink (UL)packet to indicate the appropriate network slice associated with thatpacket.

In some embodiments, the NS ID may be obtained by the mobile device viaunicast or multicast communication. For example, a mobile device maytransmit an initial message, such as a network attach request, and anetwork access node may transmit a message indicating the NS ID back tothe mobile device in response to the initial message. The mobile devicemay then include the NS ID in a network slice association message. Insome embodiments, multiple NS IDs may be transmitted to the mobiledevice, and the mobile device may select one NS ID for inclusion in thenetwork slice association message.

In some embodiments, after an initial network slice associationdetermination made by the CM, control plane packets are forwarded by theCM to a local service-specific connection manager which is specific tothe network slice to which attachment is being made. An initial networkslice association may indicate the initial associations between networkslices and UEs. In some embodiments, initial slice associations may besubsequently changed or overridden by the CM or another entity.

Following the initial network slice association, control plane packetscan be forwarded to a service-specific connection manager (CM) orcustomer service manager (CSM) or to a legacy or service specific MME.Data plane packets can be forwarded to a service specific SGW (v-s-SGW).Forwarding may be performed by a responsible packet handling entity,such as a base station or access point-type entity at the edge of thecore and radio access network. Other nodes will serve these forwardingand management functions at different points in the network topology.

Network Slice Association Details

Embodiments of the present invention relate to a method, apparatus andsystem for establishing a connection between a UE and a selected networkslice. As discussed above, the connection manager may either be locatedat a base station or access point-type entity communicating directlywith the UE, or at another location in the network infrastructure.Particular connection establishment procedures corresponding to variousembodiments of the present invention are described below.

According to some embodiments, the UE transmits an attach request to aserving access node (AN), in association with a given service request tobe accommodated by a network slice. The UE may send a separate attachrequest for each service request. The AN may be a base station or accesspoint-type entity. The attach request may include a network slice ID (NSID), if known. Each network slice is associated with a network slice ID(NS ID) by which it can be unambiguously identified. The NS ID can beobtained by the UE, for example via receipt of messages transmitted bythe network and indicative of available NS IDs. In some embodiments,information indicative of available NS IDs can be included in anexisting or dedicated SystemInformationBlock (SIB). Mechanisms forobtaining the NS ID include receiving the NS ID via customerpre-configuration or via a broadcast, unicast or multicast message. Asan alternative, the UE may transmit another ID, which is correlated withthe NS ID by an entity within the network for example via a table lookupoperation.

In some embodiments, when a UE can attach to one of a plurality ofnetwork slices, or when the UE is permitted to attach concurrently totwo or more of the plurality of network slices, the UE may select an NSID corresponding to a network slice to which attachment is to be made.The UE then indicates which network slice an attach request pertains toby including the corresponding NS ID in its transmitted attach request.

In some embodiments, the UE is configured to include an identificationof a type of network slice, selected from a plurality of types, in theattach request. Types of network slices can include MBB slice, MTCslice, and critical MTC slice, for example. The UE can identify the typeof network slice by transmitting parameters such as network servicedescription parameters as part of an attach request or other message. Insome embodiments, a UE is configured to indicate its network servicerequirements in the attach request. The requirements may include latencyand bandwidth requirements, QoS requirements, network resourcerequirements, and cost requirements, for example. A network sliceassociation function, for example of the global connection manager, maybe configured to determine which slice to select for association withthe UE based at least in part on the identification of type of networkslice or the indicated requirements.

In some embodiments, a corresponding SystemInformationBlockType (SIBType) is defined for each network slice that has been instantiated. EachSIB Type can convey information related to its corresponding networkslice, such as NS ID and descriptive information.

In some embodiments, a single SIB Type can be defined and used todescribe multiple, and possibly all, network slices that have beeninstantiated, for example in a particular region. The common SIB Typecan convey information related to multiple corresponding network slices,such as NS ID and descriptive information.

In some embodiments, the NS IDs of appropriate network slices availablefor each UE may be stored in a Home Subscriber Server (HSS). Followingauthentication of a UE, the HSS may compile and transmit a list of NSIDs to which the UE can request attachment.

In some embodiments, when the (global) connection manager is located atan access node (AN) and thus the network slice association is performedat the AN, the AN performs a NAS node selection function by selecting aservice-specific CM of a network slice indicated by the NS ID containedin the attach request. The AN then forwards the attach request to theselected service-specific CM.

In some embodiments, when the (global) connection manager is located inthe network infrastructure, for example as a VNF in the network separatefrom the AN, the AN forwards the attach request to the separateconnection manager. The connection manager then determines a networkslice to associate with the UE and selects a service-specific CM of thedetermined network slice. The connection manager then forwards theattach request to the selected service-specific CM. Alternatively, theconnection manager may transmit the network slice association operationto the AN, which then selects a service-specific CM of the determinednetwork slice and forwards the attach request thereto. The network sliceassociation operation transmitted to the AN may comprise a message whichincludes a NS ID of the determined network slice.

In various embodiments, the service-specific CM initiates anauthentication procedure in association with the service-specificAuthentication, Authorization and Accounting (AAA) server and/or HSS. Ifthe UE is determined to be authorized, the service-specific CM sends anattach response indicating the UE is admitted. The attach response mayinclude a NS specific parameter such as a NS specific UE ID.

In some embodiments, the UE may send an attach request withoutnecessarily reading the broadcast channel to determine the NS ID. Inthis case, the NS ID may be associated with the UE ID a priori, forexample by pre-programming the NS ID into the UE by customerpre-configuration. The attach request may then be configured to includeboth the UE ID and the NS ID. In some embodiments, a network service maybe associated with a network slice type, which may be associated withthe NS ID. This approach may be used for example when the UE is onlycapable of or authorized to attach to a certain pre-defined networkslice, such as when the UE is a MTC device attaching to an MTC server.

In some embodiments, the (global) CM is configured to determine the NSID based on the UE ID. In this case, the UE does not need to obtain theNS ID, for example by reading the broadcast channel. Rather, the UE IDand NS ID are pre-associated and can be determined by the CM. In thiscase the attach request includes the UE ID but excludes the NS ID. Thisapproach may be also be used when the UE is only capable of orauthorized to attach to a certain pre-defined network slice.

In more detail, and in relation to the above, FIG. 3 illustrates aconnection establishment procedure in accordance with some embodimentsof the present invention. In such embodiments, the Global Connection andMobility Manager (G-CMM) is located in the network infrastructure andperforms the network slice association. A UE 305 transmits an attachrequest 345 to an AN 310, which forwards the attach request to the G-CMM315. The attach request 345 includes a NS ID. The G-CMM determines aservice-specific CM 320 specific to an appropriate network slice, basedon the NS ID indicated in the attach request 345.

FIG. 4 illustrates a connection establishment and/or attachmentprocedure in accordance with another embodiment of the presentinvention. In this case, the G-CMM is at least partially located at anaccess node (AN) and performs the network slice association. A UE 405transmits an attach request 440 to an AN 410. The attach request 440includes a NS ID. The AN determines 445 a CM 415 specific to anappropriate network slice, based on the NS ID indicated in the attachrequest 440. This determination may be performed by the G-CMM integratedinto the AN 410.

Having further regard to FIG. 3 and FIG. 4, the attach request isforwarded 352, 447 to the service-specific CM 320, 415 and anauthentication procedure 355, 450 between the service-specific CM 320,415 and the AA 325, 420 is performed. Following successfulauthentication, the service-specific CM 320, 415 transmits a flowconfiguration request 357, 452 to a FM 330, 425. The FM performs pathcomputation operations 360, 455 and then the FM, in conjunction with anapplication server (AS) 335, 430 and the SDN-C 340, 435, performs pathconfiguration operations 362, 457.

Also, the FM 330, 425 transmits a flow configuration acknowledgementmessage 365, 460 to the service-specific CM 320, 415. Further attachresponse messages 367, 368, 369, 460, 465, 467 are propagated throughthe G-CMM and AN to the UE. Control plane messaging 370, 470 and dataplane messaging 375, 475 may follow. Alternatively, control planemessaging and data plane messaging may not be performed immediately butrather may be deferred until after a service request is received and/ornetwork traffic is present.

In various embodiments, if it is determined during authentication thatthe UE is authorized to attach to the network slice, theservice-specific CM is configured to send an attach response indicatingthe UE is admitted to the network slice. The attach response may includea NS-specific parameter such as a NS-specific UE ID identifying thenetwork slice.

In various embodiments, in order to facilitate network slice associationdetermination operations made in the network, solutions similar to thoseproposed in the 3GPP document TR 23.707, “Architecture Enhancements forDedicated Core Networks; Stage 2,” V. 13.0.0, Dec. 17, 2014, may beemployed. A first such solution corresponds to a redirection afterupdate location procedure, for example as identified in Section5.2.1.1.1.2.1 of TR 23.707. A second solution corresponds to re-routingbefore NAS security setup, for example as identified in Section5.2.1.1.1.2.2 of TR 23.707. A third solution corresponds to“null-NRI”/“null-MMEGI” based redirection, for example as identified inSection 5.2.1.1.1.2.3 of TR 23.707. A fourth solution corresponds to MMEtriggered handover, for example as identified in Section 5.2.1.1.1.2.4of TR 23.707. These solutions can be implemented in order to assign adedicated MME.

In various embodiments, for example in association with some or all ofthe above connection management operations, the attach request providedby the UE is redirected to a dedicated MME associated with the networkslice identified in the attach request.

FIG. 5 illustrates a network slice association procedure, according tosome embodiments of the present invention. With reference to FIG. 5, aG-CMM 515 selects an appropriate service-specific CMM 520 and forwardsboth the NS ID and an identifier of the selected CMM to an access node510. This is performed to redirect a UE's attach request to the selectedservice-specific CMM. In more detail, a UE 505 transmits an attachrequest 525 to the AN 510. The AN 510 forwards the attach request to theG-CMM 515 residing in the network. The G-CMM then makes a network sliceassociation operation 535, corresponding to a determination 535 of whichslice the UE is to attach to. Such a determination may be performed forexample when a particular network slice is not identified in the attachrequest. Additionally, the G-CMM may optionally select theservice-specific CMM 520 associated with the determined network slice.The G-CMM then transmits a message 540 to the AN 510 indicative of theNS ID of the determined network slice, along with an indication of theselected service-specific CMM, if applicable. If an indication of aselected service-specific CMM is not provided to the AN, or if theindication is invalid, the AN 510 may optionally select 545 theservice-specific CMM for example based on the NS ID. The AN thenforwards the attach request message 550 to the selected service-specificCMM 520. The service-specific CMM, or more specifically a CM portionthereof, initiates an attachment procedure and transmits an attachresponse message 555 to the AN 510. The AN forwards the attach responsemessage 560 to the UE 505.

Alternatively, in some embodiments, the G-CMM forwards the attachrequest to the service-specific CM directly after determining thenetwork slice association. In this case, the AN forwards the attachrequest to the G-CMM. The G-CMM performs the network slice associationoperation, and forwards the attach request to the selected CMM. Therequest specifies the serving AN. The CMM then sends the attach responseto the G-CMM, which then forwards the response to the serving AN.

As yet another alternative, in one embodiment the service-specific CMMreceives the attach request directly from the G-CMM, as illustrated inFIG. 6. In more detail, a UE 605 transmits an attach request 625 to anaccess node (AN) 610 such as an eNB. The AN 610 forwards the attachrequest to a G-CMM 615 residing in the network. The G-CMM then performsa network slice association operation 635, corresponding to adetermination 635 of which slice the UE is to attach to. Additionally,the G-CMM selects a service-specific CMM 620 associated with thedetermined network slice. The G-CMM then transmits an attach requestmessage 650 to the selected service-specific CMM 620. Theservice-specific CMM initiates an attachment procedure and transmits anattach response message 655 to the AN 610. The AN forwards the attachresponse message to the UE 605.

Because the AN determines the network slice association based on thecontents of the NAS message containing the attach request, theconnection establishment procedure is configured to include a networkslice association function. The network slice association function isperformed before the NAS Node Selection function, which selects aparticular local (service-specific) CMM for the UE.

In some embodiments, various UE devices, such as MTC devices, may beassociated with a Service ID (SID), such as a MTC SID. The serving AN isconfigured to determine the associated SID based on a substantiallyunique ID of the UE device, such as its MTC ID. For example, the servingAN can specify the UE device ID in a lookup operation performed on alocal or remote lookup table, the lookup operation returning the SIDcorresponding to the UE device ID. The serving AN is configured to thenforward the MTC traffic to an IP address corresponding to the MTC SID,which is mapped to a NS ID.

FIG. 7 illustrates signaling flow associated with an attach request, inaccordance with embodiments of the present invention. As illustrated,the attach request propagates from the UE through the control andmanagement plane 700 and service-specific control plane 702.Authentication and authorization are initiated within theservice-specific control plane. Forwarding rules are established inassociation with the SDN-C of the cloud-based core network (C-Core) 704.An attach response is propagated back to the UE.

In more detail, the process illustrated in FIG. 7 includes obtaining, bythe UE 705, the NS ID from the broadcast channel, or retrieving acustomer-pre-defined NS ID. The process further includes receiving, fromthe UE, an attach request 730 associated with a service request at aRAT-A access node 710. In some embodiments, the attach request includesa network slice identifier (NS ID). In other embodiments, the attachrequest does not include a NS ID. The process further includes, by theCM function 712, determining 735 a service-specific connectionmanagement (CM) function 715 in a service-specific control plane 702that corresponds to a particular network slice. When the attach requestincludes a NS ID, the network slice may be as indicated by the NS ID.The process further includes forwarding the attach request to theservice-specific connection management (CM) function 715. The processfurther includes performing, by the CM function, an authenticationand/or authorization procedure 740 indicative of whether the UE isauthorized for access to the network slice. The procedure may includeinteraction between the service-specific CM function 715, an HSS 717 andan AAA server 720. The process may further include establishing, by theservice-specific CM function, establishing 745 signaling and databearers, and establishing forwarding rules 750, both supporting theattachment of the UE to the network slice. The process further includes,when the UE is authorized for access to the network slice, sending anattach response 755 to the UE indicative that the UE is admitted. APHY-A node 722 in the data plane and a SDN-C 724 in the C-Core 704 arealso illustrated, the SDN-C receiving the forwarding rules 750.

When the attach request does not include a NS ID, both the NS and the CMmay be determined 735 by the CM function 712. For example, the attachrequest provided by the UE may include a UE identifier (UE ID) or otherinformation, and the CM function may determine the NS ID based on thisprovided information.

Network Architecture

Embodiments of the present invention provide for communication networkcontrol plane and/or data plane functions for supporting networkoperations in general and network slicing operations in particular. Thedata plane functions may be used to facilitate operation of the networkslices. Control plane functions include one or more of: connectionmanagement functions such as global connection and mobility management(G-CMM) functions; local or service-specific connection management (CM)or connection and mobility management (CMM) functions for exampleresiding in specific network slices; flow management (FM) and trafficengineering (TE) functions; authentication and authorization (AA)functions; global customer service management (G-CSM) functions; andlocal or service-specific customer service management (CSM) functionsfor example residing in specific network slices. Data plane functionsinclude one or both of: data analytics (DA) manager functions; andcaching and forwarding (CF) manager functions. Throughout the presentdisclosure, a CMM function may be replaced with one or both of aconnection management (CM) function and a mobility management (MM)function.

In various embodiments, a global function is configured to operate incoordination with one or more local or service-specific functions of thesame type. For example, a G-CMM may operate in coordination with one ormore service-specific CMMs (or CMs and/or MMs), and/or a G-CSM mayoperate in coordination with one or more service-specific CSMs. Thecoordinated operation may comprise message passing between functions.The local or service-specific functions may operate at least partiallyunder the direction of the corresponding global function. For example,the global function may configure operating parameters of the localfunction. In some embodiments, the global function may handle operationsof an inter-slice scope, while the local functions may handle operationsof an intra-slice or service-specific scope. The global and localfunctions may provide a distributed overall function having a branchedstructure, with the global function as the root node and the localfunctions as branch nodes.

FIG. 8A illustrates an overview of the communication networkarchitecture in accordance with embodiments of the present invention. ANetwork Function Virtualization Management and Orchestration (NFV-MANO)entity 835 includes an orchestrator function 840, a virtual networkfunction manager (VNFM) function 845 and a virtual infrastructuremanager (VIM) function 850. According to some embodiments, thefunctionality of the orchestrator function 840, VNFM function 845 andVIM function 850 can be as defined in ETSI GS NFV 001 and ETSI GS NFV002, for example. It should be appreciated that the NFV-MANO asillustrated in FIG. 8A provides one way to conceptually and/orfunctionally organize network operations, however other ways oforganizing network operations may also be used.

According to embodiments, the VIM function 850 is configured to managethe network function virtual infrastructure (NFVI) 805 which can includephysical infrastructure, virtual resources and software resources in aNFV environment. For example physical infrastructure can includeservers, storage devices network interfaces, etc. Virtual resources caninclude virtual computing machines. According to embodiments, there canbe plural VIM functions within a particular NFV architecture, whereineach VIM function is responsible for the management of its respectiveNFVI.

According to embodiments, the VNFM function 845 can be configured tomanage the virtual network functions (VNF) and can manage the lifecycleof the VNFs. For example the VNFM function 845 can create, maintain andterminate VNF instances, which can be installed on virtual machines thatare created and managed by the VIM function 850. The VNFM function 845can also be configured to provide fault management, configuration,accounting, performance and security management (FCAPs) of the VNFs. Inaddition, the VNFM function 845 can be configured to scale-up andscale-down one or more of the VNFs which can result in the scaling-upand scaling-down of the usage of one or more central processors whichprovide computational power for realizing the VNFs. In some embodiments,each VNFM function manages a separate VNF or a single VNFM functionmanages multiple VNFs.

According to some embodiments, the orchestrator function 840 isconfigured to coordinate, authorize, release and engage the NFVIresources by interaction with the VIM function 850. The orchestratorfunction 840 may also be configured to support end-to-end servicecreation between different VNFs by interaction with the VNFM function845.

FIG. 8A further illustrates a plurality of network slices and a globalcontrol plane 810 used for network slice management. The global controlplane 810 controls functions across multiple and potentially all networkslices of the communication network. The global control plane 810 may beregarded as a separate network slice in some embodiments. Theillustrated network slices include at least one Mobile Broadband (MBB)network slice 820 and at least one Machine Type Communication (MTC)network slice 815; although other types of network slices may beprovided.

In some embodiments, both the global control plane functions and theservice-specific control planes functions are instantiated at desiredlocations in the network by the NFV-MANO entity, to provide connectionmanagement across a plurality or all of the network slices. The locationof these functions may depend on performance criteria such as delayrequirements of different network services being provided.

The functions configured within the global control plane 810 can includea connection manager such as the global connection and mobilitymanagement (G-CMM) function 882, an infrastructure management (IM)function which can contain a broker function and a negotiator functionfor obtaining computing, storage and network resources for core networkfunctions. In some embodiments the IM function contains a spectrumbroker (IM-SB) function 860 which is configured to obtain spectrumresources. Data Analytics (DA) function 865 and the cache and forwarding(CF) function 870 can be instantiated within a global control plane 810.In some embodiments, DA 865 may be instantiated within control plane 810but have the ability to monitor traffic within the data plane, while inother embodiments, DA 865 may be instantiated within the data plane(possibly with a second instantiation within the control plane 810).

In more detail, the G-CMM function 882 is configured to maintain a listof instantiated network slices and parameters associated with eachnetwork slice. Parameters may include, for example, Operator ID andservice type. The G-CMM function 882 is further configured to maintain apool of connection and mobility management (CMM) functions, wherein eachCMM function is instantiated as a local service-specific functioncorresponding to a particular network slice. The G-CMM function 882 isfurther configured to perform the initial association of a UE to anetwork slice, as previously described.

The G-CMM function 882 may operate across multiple network slices whichare involved with connection and mobility management for multipleslices. In certain embodiments the G-CMM function 882 may performadditional functions. For example, the G-CMM function 882 may determinewhich network slice a User Equipment (UE) should attach to in responseto an attach request. This may include determining which network slicehandles portions of the attach request. Alternatively, the G-CMMfunction 882 may perform network slice association using extendedcapabilities of the access node 800. The G-CMM function 882 may alsomanage each network slice during roaming. For example, the G-CMMfunction may handle intra-operator inter-slice roaming, and/orinter-operator roaming. When handling inter-operator roaming, the G-CMMfunction 882 may send an inter-operator handover request to the G-CSM,or send an inter-operator handover request to a target G-CMM. The G-CMMfunction 882 may also assign a UE, currently associated with access node800, to a different network slice upon determining that the UE hasroamed outside a coverage area of the network slice. This may assist inproviding a seamless or near-seamless slice handover. The G-CMM function882 may also track a UE's association with one or more network slices.

Having regard to the above, a method is provided for managing a mobiledevice attach request in a communication network having a plurality ofnetwork slices, according to an embodiment of the present invention. Themethod includes instantiating a global connection and mobilitymanagement (G-CMM) function in the communication network. The G-CMMfunction is configured to operate across the plurality of networkslices. The method includes selecting an appropriate network slice fromthe plurality of network slices with the G-CMM function. The methodfurther includes attaching the mobile device to the appropriate networkslice. In some embodiments, the communication network includes an accessnode with which the mobile device is associated, and the method furtherincludes determining and attaching, by the G-CMM function, the mobiledevice to the appropriate network slice using extended capabilities ofthe access node.

Having further regard to the above, a method is provided for performinga network slice handover from a first operator infrastructure to asecond operator infrastructure. The method includes receiving a handoverrequest from a network slice associated with the first operatorinfrastructure. The method further includes transmitting the handoverrequest to at least one of a global customer service management (G-CSM)function and a global connection and mobility management function(G-CMM) instantiated in the second operator infrastructure.

Having further regard to the above, a method is provided for managing amobile device roaming between a first coverage area associated with afirst network slice and a second coverage area associated with a secondnetwork slice. The method includes associating the mobile device withthe first network slice when the mobile device is in the first coveragearea. The method further includes associating the mobile device with thesecond network slice when the mobile device is in the second coveragearea.

Having further regard to the above, a method is provided for managing amobile device associated with a first network slice in a communicationnetwork. The method includes instantiating a global connection andmobility management (G-CMM) in the first network slice. The methodfurther includes determining if the mobile device is in a coverage areaof the first network slice with the G-CMM function. The method furtherincludes assigning the mobile device to a second network slice when themobile device is outside of the coverage area of the first networkslice.

It will be understood that mobile UEs can move from a slice associatedwith a first operator to a slice associated with a second operator. Thiscorresponds to a slice-enabled version of an operator-to-operatorhandover as described in existing wireless standards. Additionallymovement of a UE from a slice of a first operator to a slice of a secondoperator may be explicitly triggered by a UE operator, such as the firstoperator. This allows the UE operator to switch service providers for avariety of reasons, such as cost and reliability of service in aparticular location.

In some embodiments and under certain circumstances, the UE operator maymove a UE from a first slice to a second slice if both slices areprovided or managed by the same operator. Such a move may be performedfor a variety of reasons. For example, in situations where the UEoperator uses a number of different infrastructure or telecommunicationservice providers, different slices may have different cost structures,and the UE operator may select a different slice to which to move the UEbased on operating cost. At various times, it may be advantageous tomove UEs, or groups of UEs, from one slice to another, for example, toreduce costs. Moving UEs between slices can also be performed toimplement load balancing, or to move UEs from a slice with a variablecost structure based on traffic to another slice with a fixed base fee.

In some embodiments, lifecycle management of the G-CMM function 882 isperformed by the VNFM function 845 Lifecycle management refers to theinstantiation, termination, scaling up/down and scaling in/out ofvirtual infrastructure. Scaling out may include instantiating new VNFs,at either the same location as another VNF in the network, or at a newlocation. Scaling in may include terminating VNFs. Scaling up ofinfrastructure may include allocating new resources to existing VNFs. Byproviding an existing VNF with a variable mix of additional processingpower, additional memory and additional bandwidth allocation (or bygenerally increasing the resources available to the VNF), an existingVNF can be made more robust and capable of handling more traffic.Scaling down infrastructure may include reducing the resources allocatedto an associated VNF. The G-CMM function 882 may be instantiated by theVNFM function 845 and/or VIM function 850. The G-CMM function 882 canalso be scaled in or out by the NFV-MANO entity 835 as required, forexample, as new network slices are instantiated or terminated.

The data analytics (DA) function 865 is configured to collect statisticsacross multiple and potentially all network slices. The informationcollected by the data analytics function can be used to optimizeperformance of network slices. The DA data can be used to help modify CFrules, and to modify the topology of a slice in a software definedtopology environment.

The cache and forward (CF) function 870 is configured to manage thecached content across multiple and potentially all network slices.Caching of content may involve storing data content closer toanticipated or frequent users.

In some embodiments, the network architecture further includes a globalcustomer service management (G-CSM) function 887 which is configured toreceive the network service (NS) requests 830 and respond to the NSrequests in cooperation with the orchestrator function 840 of theNFV-MANO entity 835. The G-CSM function 887 is configured to maintain apool of customer service management (CSM) functions. Each CSM functionis instantiated as a local service-specific function corresponding to aparticular network slice. Service-specific CSM functions may includecharging, QoE control, and UE context management related to charging andQoE, for example. The G-CSM function 887 is further configured to trackand/or perform charging operations, for example customer billingoperations, across multiple or potentially all network slices. The G-CSMfunction 887 can be configured to monitor network slices and providefeedback to the orchestrator function 840 indicating the performance ofnetwork slices. The feedback may be used perform fine-tuning of thenetwork and its computing resources, as managed by the VNFM function 845and the VIM function 850.

Another method for managing a customer service request in acommunication network is described as follows. The method includesinstantiating 610 a global connection and mobility management (G-CMM)function in the communication network. The method further includesreceiving 620 the customer service request by the G-CMM function. Themethod further includes determining 630 if the customer service requestcan be accommodated using an existing networks slice. The method furtherincludes instantiating 640 a new network slice to accommodate thecustomer service request when the customer service request cannot beaccommodated using the existing network slice.

According to some embodiments, the G-CSM function 887 can befunctionally integrated within the Operational Support System/BusinessSupport System (OSS/BSS) 825. The OSS can be configured to supportback-office activities which aid in operating a communication network.The OSS can be configured to provision and maintain customer services.The BSS can include support customer-facing activities, for examplebilling order management, customer relationship management, and callcentre automation. In some embodiments, the G-CSM function 887communicates with the orchestrator function 840 using the OS-MA-NFVOinterface, which provides communication between the OSS/BSS 825 and theorchestrator function 840.

According to some embodiments, the G-CSM function 887 can beinstantiated within the network but external to the OSS/BSS 825. In thisconfiguration, another interface, which is not necessarily definedwithin the present NFV framework, is configured to provide communicationbetween the G-CSM function 887 and the orchestrator function 840.

In some embodiments, the G-CSM function 887 is configured to handleinter-operator roaming. This may comprise changing a UE's attachmentstatus from a network slice of a first operator to a network slice of asecond operator, or responding to a UE changing its attachment status.

With further reference to FIG. 8A, various network slices, for examplethe MBB slice 820 and MTC slice 815, may each include their ownservice-specific connection and mobility management (CMM) functions 881,880 and/or their own service-specific customer service management (CSM)functions 886, 885. The service-specific CMM functions 881, 880 may beinvoked and at least partially controlled by the G-CMM function 882operating within the global control plane 810. Each network slice mayfurther include a flow management (FM) and/or traffic engineering (TE)function 876, 875 which can be configured to tune the performance of thenetwork slice by dynamically analyzing, predicting and regulatingbehaviour of data transmitted over that network slice. In addition, eachof the network slices may further include an authentication andauthorization (AA) function.

The CMM functions 880, 881 may be service-specific VNFs, and functionsmay perform connection management (CM) and mobility management (MM)functions. The MM functions may be instantiated on an “as needed” basisaccording to the network slice.

Connection management functions may include handling UE attachment tonetwork slices, legacy support functions including, Domain Name Service(DNS) functions, Dynamic Host Configuration Protocol (DHCP) functions,determining cloud candidate sets for UEs (e.g. the set of possible cloudservices that the UE may need access to, or the set of possible couldservices that can be used to serve the UE requirements), and determiningpower saving operating parameters, as will be apparent to those skilledin the art. Legacy support functions may include bearer management,Packet Data Network Gateway (PDN GW) selection, and SGW selection. DNSfunctions may include resolving logical names to Internet Protocol (IP)addresses for Evolved Packet Core (EPC) nodes. DHCP functions mayinclude delivering IP configuration information to/for UE's. Powersaving operating parameters may include discontinuous reception (DRX)cycles in connected or idle mode, which can be based on a power savingspolicy.

A method for performing connection management (CM) in a communicationnetwork, according to an embodiment of the present invention, isdescribed as follows. The method includes providing a network slice. Themethod further includes attaching a mobile device to the network slice.The method further includes instantiating a CM function in the networkslice. The method further includes determining a cloud candidate set forthe mobile device using the CM function. The method further includescommunicatively coupling the mobile device to the cloud candidate set.

A power savings method for a mobile device communicatively coupled to acommunication network is described as follows. The method includesproviding a network slice. The method further includes attaching themobile device to the network slice. The method further includesinstantiating a connection management (CM) function in the networkslice. The method further includes determining power savings operatingparameters with the CM function. The method further includes managingpower of the mobile device according to the power savings operatingparameters.

Mobility management functions may include one or more of: Evolved Packetsystem connection management (ECM) idle UE reachability functions,tracking UE locations, tracking area list management or paging (forexample, when uplink beaconing is not used), and roaming. MM functionsmay also be optionally configured when required by a network service.Tracking UE locations may include UE location tracking using uplinkbeacons, and UE location prediction functions.

In certain embodiments, the CM and MM functions may be combined into asingle CMM VNF having component CM and MM functions. In this case, theMM component function may be configured upon being required by thenetwork slice. In other embodiments, the CM and MM functions maycomprise separate VNFs. The MM VNF may be instantiated on an as-neededbasis.

Lifecycle management of the CMM functions 880, 881 may be performed bythe VNFM function 845. The CMM functions 880, 881 may comprise elementmanager (EM) functions (not shown) which can be internal or separate tothe CMM functions 880, 881. In certain embodiments, the CMM functions880, 881 may transmit performance metrics to the EM or VNFM function845. In response, the EM or VNFM may trigger a scale-in or scale-outoperation, for example as VNFs are instantiated or terminated.

In some embodiments, each network slice further includes aservice-specific infrastructure management function containing aspectrum negotiator function (IM-SN) 891 890. In some embodiments, theIM-SN function is external to its associated network slice, for exampleresiding within a set of Cloud Radio Access Network (C-RAN) functions.

In some embodiments, there is provided a method for scaling networkslices in a communication network. The method includes instantiating aconnection and mobility management (CMM) function within at least onenetwork slice. The method further includes determining performancemetrics using the CMM function. The method further includes scaling thenetwork slices according to the performance metrics determined by theCMM function.

Although only a single access node 800 is shown in FIG. 8A for clarityand illustrated by the “tower icon”, it will be readily understood thatmultiple access nodes are supported. In embodiments, an access nodethroughout the various figures may correspond to one or more RemoteRadio Units (RRUs) operatively coupled to one or more Baseband Units(BBUs) or the like.

In accordance with embodiments of the present invention, the NFV-MANOentity 835 further includes NFV management plane functions configuredto: define the network topology for a network service (NS) request;determine the transport protocols to be used across links; and determinethe physical links between different network functions used by thenetwork service. In some embodiments, the NFV management plane functionsare integrated within the orchestrator function 840 and include asoftware defined topology (SDT) function 897, a software definedprotocol (SDP) function 896 and a software defined resource allocation(SDRA) function.

According to embodiments, the SDT function 897 is instantiated as partof the orchestrator function 840. The SDT function 840 is configured todetermine the Point of Presence (PoP) for each VNF in the VNF forwardinggraph (VNFFG) provided by the G-CSM function 887. The SDT function 840is also configured to determine the logical links between the VNFs inthe VNFFG.

According to embodiments, the SDRA function is configured to selectphysical links for supporting each logical link defined in the VNFFG.The SDRA function includes two functional components, namely the SDNController (SDN-C) function 893 and the traffic engineering (TE)function 895. The SDN-C function 893 is instantiated within each VIMfunction 850 and is configured to provide forwarding rules for use bythe forwarding switches, for example routers and the like within thephysical network architecture. The TE function 895 is instantiatedwithin the orchestrator function 840 and is configured to perform pathcomputations for determining data communication paths to be used betweensource nodes and destination nodes in the network. The computed pathsmay be selected and configured to provide adequately high performance.The computation may include dynamically analyzing, predicting andregulating behaviour of data transmissions. In one embodiment, the TEfunction performs only the path computation between the source node anddestination node of each flow. The forwarding rules are then transmittedto the SDN-C function via the VIM function using the OR-VI interface(Orchestrator-to-Virtual Infrastructure). In another embodiment, the TEfunction performs the path computation and also determines the capacitybounds for some or all physical links for some or all network slices.The capacity bounds are sent to the flow management (FM) function ineach network slice, which performs flow splitting to limit or avoidviolating the capacity bounds. The capacity bounds are transmitted viathe OR-VI interface to the VIM function. The VIM function thendetermines and transmits the forwarding rules to the SDN-C function andthe FM function. In general, the traffic engineering and flow managementcalculations can be distributed in different ways between the TEfunction and FM function. The information exchanged between the TEfunction and the FM function is transmitted from the orchestratorfunction to the VIM function using the OR-VI interface. The VIM functiontransmits the rules to the SDN-C function and the SDN-C functiontransmits information to the FM function for flow-management-relatedcalculations. Those skilled in the art will appreciate that at eitherextreme of the distribution of the functionality between TE function andFM function, one of the entities can be assigned all responsibilities,while the other is assigned none. It should be noted that both of theseextreme cases, along with blends between the two, can be supported.

In some embodiments of the present invention, traffic engineeringoperations are allocated between the TE function and FM functions in thenetwork architectures of FIGS. 8A to 8C in at least three differentways. First, the TE function may perform path computations to determinethe capacity bounds for each physical link for each network slice. TheFM function may then split the flows along predetermined paths, whileattempting to respect per-slice capacity bounds. Second, the TE functionmay perform both path computation and flow management across multiple orall links and network slices, thereby precluding the need to instantiatethe FM function for certain network slices. Third, the TE function mayperform path computation and determine capacity bounds for each physicallink for each network slice. These computations can be done on aper-service basis instead of a per flow basis. Because the computationsdo not consider flows, it may allow the preclusion of the need toinstantiate the FM function for certain network slices.

A method for transmitting packets between a source node and adestination node in a communication network is described as follows. Themethod includes associating a network slice with the source node. Themethod further includes instantiating a flow management (FM) function inthe network slice. The method further includes instantiating a trafficengineering (TE) function in the communication network. The methodfurther includes performing, using the TE function, path computations todetermine paths and capacity bounds for links between the source nodeand destination node for the network slice. The method further includessplitting flows along the determined paths using the FM function. Themethod further includes transmitting packets between the source node andthe destination node along the determined paths. The method furtherincludes managing flows to attempt to ensure that the determinedcapacity bounds are respected using the FM function.

A method for transmitting packets between a source node and adestination node in a communication network is described as follows. Thesource node is associated with a network slice. The method includesinstantiating a traffic engineering (TE) function in the communicationnetwork. The method further includes performing, using a TE function,path computations to determine paths and capacity bounds for linksbetween the source node and destination node for the network slice. Themethod further includes transmitting packets between the source node andthe destination node according to the determined paths. The methodfurther includes managing traffic to attempt to ensure that thedetermined capacity bounds are respected, using the TE function.

According to embodiments, the SDP function 896 is instantiated as partof the orchestrator function 840. The SDP function 896 is configured todetermine the transport protocol stack for each of the logical linksdefined in the VNFFG.

In some embodiments of the present invention, an authentication andauthorization (AA) function is provided and configured to performfunctions including: UE identity check, location updating, andauthentication. For example, an AA VNF may be instantiated for eachnetwork slice. The AA VNF can communicate with a CM so that the CM canobtain authentication information of a UE during an attach request. TheAA VNF may also be communicatively connected to AA VNFs of other networkslices to provide or obtain AA related services.

FIG. 8B illustrates an overview of the communication networkarchitecture in accordance with another embodiment of the presentinvention. The illustrated architecture is similar to that of FIG. 8A,except that the G-CMM function 882 which controls the service-specificCMM functions of the individual network slices is removed from theglobal control plane 810 and integrated with the access node 800. Inthis embodiment, the IM-SB function 860 can also be integrated with theaccess node 800 along with the G-CMM function 882.

FIG. 8C illustrates an overview of the communication networkarchitecture in accordance with another embodiment of the presentinvention. The illustrated architecture is similar to that of FIG. 8A,except that a slice management control plane 855 is further providedwhich includes the G-CMM function 882 and the IM-SB function 860. Theslice management control plane 855 is instantiated either at the RAN orat another location within the network architecture, while beingseparated from the access node 800 and the global control plane 810.

Network Slice Instantiation

Embodiments of the present invention relate to a method, apparatus andsystem for performing network slice instantiation. Network slices can beinstantiated dynamically in response to a need or in anticipation ofsuch a need. Network slices can be instantiated in a variety of ways andwith a variety of features and configurations.

In some embodiments, a network slice of a first type is provided. Someor all network slices of a communication network may be of the firsttype. The network slice of the first type includes control planefunctions but does not necessarily include all data plane functionsrequired for the network slice's operation. Rather, some or all of thedata plane functions may reside outside of the network slice, and may beshared between multiple network slices. The control plane for thenetwork slice is instantiated separately by the NFV-MANO entity.Further, the control plane functions of a network slice of the firsttype are isolated from other network slices. A function included in anetwork slice uses the resources allocated to the network slice, such ascommunication, computing and memory resources, to carry out itsoperation.

In some embodiments, the instantiated network slice is configured toinclude control plane functions for exclusive use by the network slice.

Further, for network slices of the first type, data plane functions maybe instantiated, either within or outside the slice, on an as-neededbasis. Data plane functions which are not required need not beinstantiated.

Data plane functions may be shared among network slices, for example byproviding a data plane function within a set of common network resourceswhich is accessible by multiple slices. The set of common networkresources may itself reside within a network slice.

In some embodiments, a network slice of a second type is provided. Someor all network slices of a communication network may be of the secondtype. The network slice of the second type is configured to include bothcontrol plane functions and data plane functions. Some or all of thedata plane functions may be provided for exclusive use by the networkslice.

In various embodiments, a request to instantiate a network slice of thesecond type contains a VNFFG. The VNFFG may contain both control planefunctions and data plane functions, if required. In some embodiments,some or all functions in the VNFFG are instantiated by the MANO entity.

In various embodiments, data plane functions belonging to a networkslice of the second type are shareable among multiple network slices. Anetwork slice may therefore exclude or share at least one data planefunction to be used by the network slice.

In some embodiments, when a network slice of the second type isinstantiated, an SDT function determines the PoPs for new functionscreated with the slice and determines the logical links between newfunctions, and between new and existing functions. In some embodiments,data plane functions are instantiated when they are specified in theVNFFG for a network service request which acts as a trigger for networkslice instantiation.

Further, for network slices of the second type, control plane functionswithin the network slice are isolated from other slices. Isolation maybe achieved by allocating dedicated sets of resources for providing thecontrol plane functions, which are separate from the resources used forproviding functions of other network slices. The sets of resources mayinclude processing resources, memory resources, and communicationresources, such as communication media and routing facilities.

FIG. 9 illustrates aspects of a network slice which may be of the firsttype or the second type, according to embodiments of the presentinvention. In a non-sliced network, traffic can be decoupled into a dataplane and a control plane. The control plane is a logical construct thatallows control messages between functions and nodes to be treateddifferently than the data transmitted between the nodes. As illustratedin FIG. 9, a similar logical construction can be used within a slice.Control of functions within the slice can be managed within a controlplane. The nodes within the data plane transmit control information andstatistics to control entities, such as the CM. The CM is a part of thecontrol plane, which governs the actions and control of the traffic inthe data plane. Both the control and data planes can include functionsinstantiated by an SDN controller.

Having reference to FIG. 10, embodiments of the present inventionprovide for a network slice instantiation procedure. The instantiationprocedure may be used for instantiating network slices of the first typeor the second type. The instantiation procedure includes receiving, at aG-CSM 1010, a customer and/or network service request 1035 from aservice operator 1005. The service request indicates that a customer hasspecific requirements to be met by a network slice. In response to theservice request, the G-CSM determines 1040 whether to select an existingnetwork slice (NS) for accommodating the service request, or to create anew network slice for accommodating the service request.

In various embodiments, the service request does not necessarilyindicate that a new slice is required. Rather the service request maycontain performance requirements for the service, such as QoSrequirements, network resource requirements, and/or bandwidthrequirements. The G-CSM receives the requirements and determines if anew slice is required based on same.

In some embodiments, an existing network slice may be selected for useif it has sufficient capacity and is appropriate to use foraccommodating the network service request. For example, an existingnetwork slice can be selected when the service functions needed tosupport the service request are already present in the slice and/or canbe instantiated in the slice, and when the admission of the new trafficcorresponding to the network service can be accommodated along withexisting requirements of the network slice. When an existing networkslice is selected, required network functions that are not present inthe slice may be instantiated and network function customizationnecessary for supporting the new network service requests can beundertaken. Functions supporting the new service may be linked to othernetwork functions potentially already existing in the slice. In someembodiments, additional resources can be added to the existing networkslice to increase its capacity.

If a new network slice is to be created, then the G-CSM transmits anetwork service (NS) request 1045 to an orchestrator 1015 of theNFV-MANO entity. The NS request can include an indication of a VNFFG tobe realized by the new network slice. In response, the orchestrator isconfigured to use its associated SDT function to determine 1050 pointsof presence (PoPs) of VNFs of the VNFFG, and logical links between theVNFs of the VNFFG. The orchestrator is further configured to use itsassociated SDP function to determine 1055 one or more transportprotocols for use by the logical links between the VNFs of the VNFFG.

Once the determinations of PoPs, logical links and transport protocolsis made, slice instantiation proceeds, for example in accordance withexisting MANO procedures. As illustrated, the orchestrator 1015transmits an instruction 1060 to the VIM function 1025 to allocateresources for use by the new network slice. The VIM function 1025performs the resource allocation and acknowledges 1062 the instruction.The orchestrator 1015 then transmits an instruction 1065 to the VNFMfunction 1020 to instantiate the VNFs specified by the VNFFG within thenew network slice. The instruction may specify information such as thedetermined PoPs of the VNFs to be instantiated. The VNFM function 1020accordingly causes the instantiation operations to be performed andacknowledges 1067 the instruction.

Subsequently, path configuration 1070 is performed. The pathconfiguration may involve operation of a traffic engineering function,for example within the orchestrator. Path configuration may involveinteraction between the orchestrator 1015 and the SDN function 1030 inorder to configure the paths. The SDN function, which may be associatedwith a SDN-C, may provide the forwarding rules for use by forwardingswitches to provide data paths between the instantiated VNFs and otherentities associated with the network slice.

Subsequently, the orchestrator transmits an acknowledgement 1075 to theG-CSM, indicative that the network slice instantiation is complete, andthe G-CSM transmits an acknowledgement 1080 to the service operator1005, also indicative that the network slice instantiation is complete.

The various details related to network slice instantiation as describedabove are examples, and can vary between embodiments.

In some embodiments, in addition to instantiating its own networkslices, an operator can also instantiate NFV-MANO functions along withthe global functions or a common MBB slice for an MVNO. For example, asillustrated in FIG. 11, an Operator A instantiates its own NS requestsand the common slice (containing global functions) for MVNO B. MVNO Binstantiates its own NS request using its own MANO. NS Requests are sentto the corresponding G-CSMs.

FIG. 12 illustrates two network slices 1210, 1220 of a first type, whichinclude their own control plane functions 1215, 1225 but which sharedata plane functions 1230 external to the two network slices. FIG. 12also illustrates a network slice 1240 of a second type, which includesits own control plane functions 1245, and its own data plane functions1250. Some or all of the data plane functions 1250 may be shared withanother slice 1260.

Network Slice Management

Embodiments of the invention provide for a method and apparatus formanaging network slices. For example, embodiments of the presentinvention provide for management plane functions for managing one ormore aspects of instantiated network slices of a communication network.

Embodiments of the present invention involve one or more managementplanes separate from the plurality of network slices, the managementplanes configured to at least partially manage each of the plurality ofnetwork slices. Global functions, such as a global connection andmobility management (G-CMM) function, and a global customer servicemanagement (G-CSM) function, can reside within such a management planeseparate from the plurality of network slices. Some or all of theplurality of network slices may provide service-specific functionscorresponding to the global functions. For example network slices mayinclude service-specific connection management and service-specificcustomer service management. Each service-specific function mayexclusively support the network slice or slices with which it isassociated.

In view of the above, embodiments of the present invention provide for amethod for managing a plurality of network slices in a communicationnetwork. The method includes providing one or more management planes setapart from the plurality of network slices, the management planesconfigured to at least partially manage each of the plurality of networkslices. The method further optionally includes configuring themanagement planes to provide one or both of connection management andcustomer service management. The method further optionally includesconfiguring the network slices to further provide service-specificconnection management and service-specific customer service management.

In various embodiments, both the management plane functions and thecontrol plane functions may be instantiated at a substantially arbitrarylocation in the network by the management and orchestration (MANO)entity in order to provide for connection management across a pluralityor all of the network slices. The location of these functions may dependon performance factors such as delay requirements of different networkservices being provided. Further embodiments of the present inventionrelate to particular arrangements of the management plane functionsand/or control plane functions within the network. For definiteness, theMANO may correspond to that entity which is defined by the EuropeanTelecommunications Standards Institute (ETSI) MANO working group.

FIG. 13 illustrates a plurality of network slices 1310, 1320 and amanagement plane 1330 used for network slice management in accordancewith embodiments of the present invention. The management plane 1330 maybe a separate network slice. The example illustrated network slicesinclude a Mobile Broadband (MBB) network slice 1310 and a Machine TypeCommunication (MTC) slice 1320, although other types of network slicesmay be provided. The MBB and MTC slices may each include their ownservice-specific connection management (CM) functions 1312, 1322 andservice-specific customer service management (CSM) functions 1314, 1324.The service-specific functions may be managed by corresponding functionsin the management plane. The service-specific CM and service-specificCSM functions within each slice may be referred to as control planefunctions. Although only a single UE 1300 and base station/accesspoint/eNB 1305 are illustrated for clarity, it will be readilyunderstood that multiple UEs and access points are supported. In variousembodiments, a base station/access point/eNB 1305 may correspond to oneor more Remote Radio Units (RRUs) operatively coupled to one or moreBaseband Units (BBUs).

Embodiments of the present invention provide for a management plane 1330which is configured to provide management functions across all networkslices. The management plane functions may include: connectionmanagement (CM) 1332; customer service management (CSM) 1334;infrastructure management (IM) 1336; data analytics (DA) 1338; andCaching and Forwarding (CF) 1340.

In various embodiments, the management plane functions differ from thecontrol plane functions. The management plane performs the functionsacross all the network slices, while the corresponding control planefunctions perform the functions for the specific network slice. Eachnetwork slice can have customized control plane functions.

In more detail, the connection management (CM) function 1332 in themanagement plane 1330 is configured to maintain a list of theinstantiated network slices and the parameters associated with thenetwork slice (e.g. Operator ID, service type, etc.). The CM function isfurther configured to maintain a pool of service-specific CMs 1312, 1322instantiated within each network slice. The CM function 1334 is furtherconfigured to perform initial association of a UE 1300 to a networkslice 1310, 1320.

The customer service management (CSM) function 1334 in the managementplane 1330 is configured to maintain a pool of service-specific CSMs1314, 1324 instantiated within each network slice. The CSM function isfurther configured to track charging across all network slices.

The infrastructure management (IM) 1336 function is configured toperform infrastructure sharing, such as sharing spectrum using aspectrum broker.

The data analytics (DA) function 1338 is configured to collectstatistics across multiple network slices.

The cache and forward (CF) function 1340 is configured to manage cachedcontent across all network slices.

FIG. 14A illustrates a network slicing configuration includinginstantiation of a management plane CM function 1410 and a managementplane CSM function 1415 in accordance with an embodiment of the presentinvention. The management plane CM and CSM functions are instantiated asand/or within separate management planes 1411, 1416. Different networkslices may be associated with different operators. A first operator,Operator A, may be associated with a first set of network slices 1420,and a second operator, Operator B, may be associated with a second setof network slices 1430. Different UEs 1440, 1442, 1444 may be associatedwith one or more different network slices.

FIGS. 14A to 14C illustrate different network architectures according todifferent embodiments of the present invention. For each networkarchitecture, three different options are illustrated for how a MANOentity can be established to serve the network slices. In Option 1 1450,for each of FIGS. 14A to 14C, different MANO entities 1452, 1454 areestablished for each different operator, and another MANO entity 1456 isestablished for the management plane. In Option 2 1460, each operator isserved by a unique MANO entity 1462, 1464, and one of the MANO entities1464 associated with an operator also serves the management planes. InOption 3 1470, all operators and the management planes are served by asingle MANO entity 1472. Differences in the architectures shown in FIGS.14A to 14C relate to how the resources of different operators can beinterconnected with each other and with a CSM management plane. One ormore MANO entities may be established, each of the MANO entitiessupporting one or more of the network slices, including management planenetwork slices. In various embodiments, each network slice is supportedby a single MANO entity.

In various embodiments, each MANO entity is responsible for lifecyclemanagement of the network services instantiated within itsadministrative domain.

FIG. 14B illustrates a network slicing configuration particularlyshowing instantiation of connection management functions, including amanagement-plane connection management (MP-CM) function 1482 residing ina management plane 1480 which may operate as described below.

The MP-CM function 1482 may handle connection management across multiplenetwork slices. Separate service-specific CM virtual network functions(VNFs) 1422, 1424, 1432 may be instantiated within each network slice tohandle the service specific connection management. Global connectionmanagement aspects may be handled by the MP-CM function 1482 andservice-specific connection management aspects may be handled by theservice-specific CM 1422, 1424, 1432 within the network slice.

In various embodiments, lifecycle management of the management planefunctions can be handled by the MANO, for example as owned by theinfrastructure provider or an operator. The operator may allow a VirtualNetwork Operator such as a Mobile Virtual Network Operator (MVNO) tomanage its own network slices with its own MANO. Alternatively theoperator may manage the MVNO network slices itself.

In some embodiments, the Mobile Broadband (MBB) network slice can beused to handle initial access for all devices instead of the managementplane.

FIG. 14B also illustrates various examples of associations between UEs1440, 1442, 1444 and network slices. A UE 1440, 1444 may be associatedwith plural network slices.

In embodiments of the present invention, the MP-CM function can be a VNFinstantiated within the management plane. Alternatively, the MP-CMfunction can be a separate connection management layer which isinstantiated as a separate network slice. The lifecycle management ofthe MP-CM may be performed by the management and orchestration (MANO)entity. For example, the MP-CM may be instantiated by the MANO, and maybe scaled in/out by the MANO as needed, for example as new networkslices are instantiated or terminated.

In some embodiments, the MP-CM may perform one or more of the followingfunctions: determining where to forward attach requests; keeping trackof the network slices that have been instantiated; subscriptionmanagement for Machine-Type-Communication (MTC) and/or Internet ofThings (IoT) devices that may be capable of associating with multipleoperators; and connection management for each network slice duringroaming. Connection management may include assigning a UE to a differentnetwork slice when the UE roams outside the coverage area of a networkslice.

In some embodiments, the MP-CM may be configured to keep track ofassociations between UEs and network slices. The service-specific CMwithin each network slice may be a service-specific VNF, such as avirtual service-specific connection manager (v-s-CM).

The MP-CM and set of service-specific CMs may be configured tocooperatively or independently provide connection management for thevarious network slices by an appropriate division of tasks.

In some embodiments, the v-s-CM VNF is configured to keep track of aUE's relative location. For example, the UE's relative location may bethe serving eNB if the UE is in CONNECTED mode, or the tracking area ifthe UE is in IDLE mode. The v-s-CM VNF may be configured to perform anauthentication procedure with the HSS, which may be a service-specificHSS containing a list of the IDs of the UEs that are authorized to usethe associated network slice (NS). The v-s-CM VNF may be configured tosend the attach response message along with the security and cipheringoptions to the device, for example via the serving eNB.

In some embodiments, the lifecycle management of the CM VNF is performedby the VNF Manager (VNFM).

In some embodiments, the CM includes an element manager (EM), such asdefined in various 3GPP specifications, which may be part of the VNF orprovided as a separate function. The EM may be configured for managingnetwork elements as would be readily understood by a worker skilled inthe art

In some embodiments, the CM may transmit performance metrics to eitherthe EM or the VNFM. The performance metrics may be used to trigger alifecycle management operation such as a scale in/out of supportingvirtual infrastructure related to the service.

FIG. 14C illustrates a network slicing configuration similar to FIG.14B, except that the customer service management (CSM) function isexplicitly illustrated. In particular, the management plane 1480includes both the MP-CM 1482 and a MP-CSM 1486, and the various networkslices 1420, 1430 also include service-specific CSM functions 1426,1428, 1436. The CSM function may operate as described below.

Generally, the MP-CSM 1486 manages the charging and QoS requirementsacross multiple network slices. Further, the service-specific CSMfunctions, 1426, 1428, 1436 can be instantiated within eachcorresponding network slice to handle charging and QoS for that networkslice. The MP-CSM 1486 may be a VNF which may be instantiated within themanagement plane layer 1480. Alternatively, the management planecustomer service management (CSM) layer may be instantiated as aseparate network slice by the MANO.

The lifecycle management of the MP-CSM or CSM layer may be performed bythe management and orchestration (MANO) entity. The MP-CSM or CSM layermay be instantiated by the MANO, and may be scaled in/out by the MANO asneeded, for example as new network slices are instantiated orterminated.

Various functionalities of the MP-CSM are as follows. It will be readilyunderstood that other functionalities may be present. The MP-CSM may beconfigured to handle the charging for various devices across all thenetwork slices. The MP-CSM may be configured to communicate with theservice specific CSM functions to determine the overall billing for eachdevice or group of devices in the case of MTC/IoT. The MP-CSM may beconfigured to ensure that the QoE can be met for each UE per networkslice, for example before that UE is admitted. The MP-CSM may beconfigured to communicate with the CM function to establish themanagement of the per user billing for the combined network slices. TheMP-CSM may be configured to provide subscription management for MTC/IoTdevices that may be capable of associating with multiple operators.Alternatively, subscription management may be performed by the MP-CM.

In various embodiments, the service-specific CSM function within a givennetwork slice may be a service-specific VNF, such as a virtualservice-specific customer service manager (v-s-CSM). It is noted thatdifferent network slices may have different service-specific CSMs.

In various embodiments, each v-s-CSM is configured to handle the servicespecific charging for one or more specified UEs, for example inassociation with a given network slice. The charging may depend onvarious factors. For example, charging may depend on the QoS requestedby the UE, the loading in the network, the time of day, or a combinationthereof. In some embodiments, the v-s-CSM may communicate with theservice specific SGW (v-s-SGW) to determine the amount of traffic sentand/or received by the subject UE. In some embodiments, the v-s-CSM maycommunicate with other entities to update the parameters used toevaluate the cost of providing the service to the UE. For example, thecost may increase if the loading in the network increases.

In some embodiments, the lifecycle management of the CSM VNF isperformed by the VNF Manager (VNFM).

In some embodiments, the CSM may also have an Element Manager (EM),which may be a part of the VNF or provided as a separate function.

In some embodiments, the CSM may send performance metrics to either theEM or the VNFM. The performance metrics may be used to trigger alifecycle management operation such as a scale in/out of supportingvirtual infrastructure related to the service.

As will be readily understood in view of the above, the MP-CSM and setof service-specific CSMs may be configured to cooperatively orindependently provide customer service management for the variousnetwork slices by an appropriate division of tasks.

Infrastructure Management

Embodiments of the present invention relate to infrastructure managementin a communication network supporting a plurality of network slices, asdescribed below.

In various embodiments comprising infrastructure management, a spectrumbroker manages spectrum sharing between plural network operators inassociation with a radio access network portion of the communicationnetwork. The spectrum sharing comprises negotiation between the spectrumbroker and the plurality of network operators. The spectrum broker mayallocate resources to the plurality of network operators or to theplurality of network slices. A spectrum negotiator function may beprovided and configured to negotiate with the spectrum broker to requestallocation of spectrum resources, for example on behalf of networkoperators or other entities requiring resources.

In view of the above, and with reference to FIG. 15 embodiments of thepresent invention provide for a method for managing infrastructure in acommunication network supporting a plurality of network slices andsupported by a plurality of network operators and/or infrastructureproviders. The method includes providing 1510 a spectrum brokerconfigured to facilitate spectrum sharing between the plurality ofnetwork operators in association with a radio access network portion ofthe communication network. The spectrum sharing includes negotiationbetween the spectrum broker and the network operators. The methodfurther optionally includes configuring 1520 the spectrum broker toallocate resources to the network operators or to the network slices.The method further optionally includes providing 1530 at least onespectrum negotiator function configured to negotiate with the spectrumbroker to request allocation of spectral resources.

FIG. 16 illustrates a network configuration including infrastructuremanagement in accordance with some embodiments of the present invention.The UE 1605 may be capable of communication on multiple carriers and/ormultiple Radio Access Technologies (RATs) 1615. The carriers may beowned by different operators. Further, various network slices may spanacross multiple infrastructure providers. A connection manager (CM) 532in the management plane 530 is provided and configured to keep track ofthe UE's subscription preferences and/or to provide the forwardingpolicy to the CMs in the network slices that are serving the UE.

In some embodiments, a spectrum broker (SB) 1636 can be instantiated toenable use of spectrum by multiple operators, for exampleopportunistically. The spectrum broker can be a part of theinfrastructure management (IM) entity 1634 for example as located in themanagement plane 1630.

In more detail, as illustrated in FIG. 16, a UE may communicate with oneor more Remote Radio Units (RRU) 1607 which are coupled to a givenBaseband Unit (BBU) 1610 supporting the plurality of RATs 1615. The RATsin turn may be operatively coupled to plural network slices, for examplenetwork slices 1640, 1650 belonging to different operators and/orassociated with the management plane 1630. Those skilled in the art willappreciate that in some instances, a single unit will have both the RRUand the BBU, while in other instances, the RRU is separate from the BBU.Context is sufficient for those skilled in the art to make such adetermination.

FIG. 17 illustrates a network configuration including infrastructuremanagement in accordance with an embodiment of the present invention. Inthis embodiment, the infrastructure may be owned by a third party, andthe data plane may utilize an opportunistic carrier.

In relation to FIG. 17, the IM entity can be used to facilitate spectrumsharing, such as via Time-Division Multiplexing (TDM) orFrequency-Division Multiplexing (FDM) or related multi-access spectrumsharing. An infrastructure management spectrum broker (IM-SB) entity1715 is provided in the C-RAN 1710 for this purpose. Each operator hasits own anchor carrier, which may be used for the control plane.Further, the opportunistic carrier, which is obtained by negotiatingwith the spectrum broker, may be used for the data plane. In someembodiments, the spectrum broker is an infrastructure managementfunction that does not belong to any VIM, but rather is owned by a3^(rd) party infrastructure provider.

Further in relation to FIG. 17, each operator instantiates its own VNFsfor both the C-RAN 1710 and the C-Core 1750. In addition, aninfrastructure manager (IM) 1755 may be included in the cloud for thecore network functions (C-Core) to obtain new resources for the corenetwork functions. The two paths 1770, 1775 illustrated in FIG. 17correspond to two different connection routes for use by differentnetwork slices. Data from different UEs will follow a path defined bythe network slice that the UE is using. The sparsely dotted blockscorrespond to radio access and core resources of one operator or set ofoperators and/or infrastructure providers and/or to radio access andcore resources associated with a first network slice. The densely dottedblocks correspond to radio access and core resources of another operatoror set of operators and/or infrastructure providers and/or to radioaccess and core resources associated with a second network slice. Fortwo network slices making use of the same physical resources, theresources can be partitioned to ensure that each slice is provided withan adequate resource base. For moderately to highly constrainedresources, such as radio links, network slices can be allocated throughthe use of multiplexing, such as a TDM or FDM technique.

In more detail, in Time Division Multiplexing (TDM) spectrum sharing,the entire carrier may be used by the same operator for the durationallocated by the spectrum broker. In Frequency Division Multiplexing(FDM) spectrum sharing, the carrier may be sub-divided, with eachoperator being allocated a portion of the carrier, and the broker beingconfigured to dynamically change the amount of resources allocated tothe different operators.

In some embodiments, the spectrum broker 1715 may be configured toallocate resources to different network slices rather than differentoperators.

In some embodiments, a virtual service-specific infrastructuremanagement (v-s-IM) VNF may be instantiated within multiple networkslices. The IM, such as the v-s-IM, within a given network slice maythen be configured to negotiate with the spectrum broker.

FIG. 18 illustrates configuration of the v-s-IM 1810, as configured tonegotiate with the spectrum broker 1832, and the relationship of thev-s-IM with other functions, in accordance with an embodiment of thepresent invention.

Having regard to FIG. 18, the illustrated v-s-IM VNF 1810 includes aspectrum negotiator function 1812 and optionally a resource requestpolicy function 1814. The spectrum negotiator function 1812 isconfigured to request spectrum resources from the spectrum broker 1832residing in the management plane infrastructure management function1830. The spectrum negotiator may be responsive to a request for morespectrum from the virtual service-specific Serving Gateway (v-s-SGW)1840 or a Radio Node 1850 when a resource request event is triggered bya resource event trigger 1842, 1852. The resource request event may beenabled when the virtual infrastructure manager (VIM) can no longerperform the scale up or scale out operation due to lack of resources.Those skilled in the art will appreciate that the VIM may be designed tosatisfy the requirements specified in the ETSI NFV structure. Thespectrum negotiator may be configured to consult the resource requestpolicy function, when provided. The resource request policy function mayeither be a part of the spectrum negotiator or a separate functionwithin the v-s-IM. Alternatively, the resource request policy functionmay be provided as a separate VNF.

FIG. 19 illustrates a spectrum negotiator function 1912, 1922 inrelation with other functions, in accordance with an alternativeembodiment of the present invention. In the embodiment of FIG. 19, thespectrum negotiator 1912, 1922 can be a function of the v-s-SGW 1910and/or the radio node 1920 rather than being provided as a separate IMentity of a network slice. In operation, a resource event trigger 1914,1924 is transmitted to the spectrum negotiator. Both functions can beco-located on the same NFVI node or they can be instantiated on separatenetwork nodes as component functions. In some embodiments correspondingto the configuration of FIG. 19, the different network nodes may use adifferent resource request policy for performing the negotiationfunction, which may be internal to each network node or as a separateVNF. Negotiation comprises communicating with the spectrum broker 1932in the management plane IM VNF 1930.

End-to-End Service Management

Potentially separately or in association with network slice association,embodiments of the present invention provide for end-to-end servicemanagement, as described below.

FIG. 20 illustrates end-to-end service management using software definednetworking (SDN), in accordance with embodiments of the presentinvention. As illustrated, an SDN controller may be instantiated in theC-RAN 2010 and/or the C-Core 2030. The SDN controller is denoted asRAN-C 2012 in the C-RAN and as SDN-C 2032 in the C-Core. The RAN-Cprovides the forwarding rules for the RAN functions. Different RANfunctions can be included in different network slices. Additionally, anSDP may determine the access protocol stack for each network slicebefore the network slice is instantiated by the MANO. The SDN-C 2032 isthe SDN controller for the core network elements. In embodiments, thedifferent network slices can have different network functions.

Also illustrated in FIG. 20 is a CM-CM interface 2050 defined betweenthe CM 2014 of the C-RAN control and management plane (MP-CM) and the CM2034 of the C-Core Control Plane (CP-CM).

In more detail with respect to FIG. 20, a data plane 2060 correspondingto a MBB network slice and a data plane 2070 corresponding to a MTCnetwork slice are illustrated. The RAN-C SDN controller 2012 in theC-RAN 2010 manages radio-access-related functions in each of theseslices 2060, 2070, such as the physical layer functions 2062, 2072, MAClayer functions 2064, 2074, and the like. The SDN-C SDN controller 2032in the C-Core 2030 manages core related functions in each of theseslices, such as the serving gateway 2082, 2092 and packet gateway 2084,2094 functions. Each of these functions may comprise virtual networkfunctions, for example.

In view of the above, and with reference to FIG. 21, embodiments of thepresent invention provide a method for end-to-end service management inan SDN-capable communication network supporting a plurality of networkslices. The method includes instantiating 2110 a first SDN controller ina C-RAN of the network. The method further includes instantiating 2120 asecond SDN controller in a C-Core of the network. The method furtherincludes configuring 2130 the first SDN controller to provide forwardingrules for RAN functions in the C-RAN. The method further includesconfiguring 2140 the second SDN controller to control network elementsin the C-Core. The method further includes providing 2150 an interfacebetween a first connection manager in the C-RAN and a second connectionmanager in the C-Core, the first connection manager operatively coupledto the first SDN controller and the second connection manageroperatively coupled to the second SDN controller.

In embodiments of the present invention, software defined networking(SDN) corresponds to an architectural framework for creating intelligentprogrammable networks, where the control planes and the data planes aredecoupled, network intelligence and state are logically centralized, andthe underlying network infrastructure is abstracted from theapplication. In embodiments of the present invention, an orchestratorfunction may use customer information and provide information to form anetwork logical topology, for example as created via the softwaredefined topology (SDT) function. The SDT function can be combined withthe SDN and software defined protocol (SDP) functions to create acustomized virtual network, wherein a virtual network is a collection ofresources virtualized for a particular service.

In some embodiments, SDN allows for the management of network servicesthrough abstraction of lower-level functionality. Control functions maybe separated from forwarding functions for example by controlling theforwarding nodes from a control element. NFV can facilitate thevirtualization of entire classes of network node functions. A VNF cancomprise or operate on one or more virtual machines running onrelatively generic servers or computing equipment, such as commercialoff-the-shelf hardware capable of being configured to provide a varietyof functionalities, as opposed to dedicated hardware for a givenfunctionality.

Various embodiments of the present invention, for example with respectto the above-described network slice association process, may be used toprovide for flexibility in the instantiation of the management planefunctions and the control plane. In some embodiments, and subject toother limitations that may arise, both the management plane functionsand the control plane can be instantiated substantially anywhere in thenetwork by the management and orchestration (MANO) entity to manage theconnection management across all the network slices. In someembodiments, determining the locations of the functions can depend onthe delay requirement of the different network services. In someembodiments, the global and/or service-specific connection managementfunctions can be located at the network edge at least in locations wherethere are devices that require fast access.

Hardware and Implementation

Some embodiments of the present invention are implemented usingcomputing devices such as servers or collections of servers, capable ofhigh-speed communication with other devices in the networkinfrastructure. Such computing devices may correspond to infrastructuredevices of the communication network. Computing devices may be dedicatedto a particular function, or provide a platform for supportingvirtualized functions. FIG. 22 illustrates a collection of standardservers 2210, data storage units 2220, and network communicationcomponents 2230 such as network interfaces and/or switches, which areprovided in accordance with embodiments of the present invention. Thecomponents may be co-located, geographically distributed, or acombination thereof. The microprocessors of the computing devices,operatively coupled to memory such as server memory and/or data storageunit memory, and the network communication components may be configuredto instantiate and execute the various functions, modules, interactionstherebetween, and the like, as described herein. Functions may beinstantiated at an appropriate network and/or geographic location, andmay be moved as required. An apparatus according to embodiments of thepresent invention may comprise the microprocessors, memory and networkcommunication components configured to perform one or more functions asdescribed herein.

It will be readily understood that, throughout the preceding discussion,the above-described network functionalities and operations maycorrespond to a method for use in supporting operation of acommunication network, such as a 5^(th) generation wirelesscommunication network. The method may involve computer-implementedfunctions, namely functions which are implemented by one or morecomputing, communication and/or memory devices of the networkinfrastructure. Further, it will be readily understood that embodimentsof the present invention relate to a communication network system orassociated apparatus thereof, which is configured to perform theabove-described network functionalities and operations. Again, thesystem or apparatus may comprise one or more computing, communicationand/or memory devices of the network infrastructure.

Embodiments of the present invention may be implemented using specificservers or general-purpose computing, communication and/or memorydevices which are configured to provide the required functionalitythrough virtualization technologies. Devices may include other hardwaresuch as Application Specific Integrated Circuits, microcontrollers, anddigital logic circuits. The method may involve the operation of one ormore network components in order to improve the operation of thenetwork. As such, with the communication network viewed as an apparatus,embodiments of the present invention may be directed to improvinginternal operations of the communication network.

Embodiments of the present invention may be implemented using one ormore real or virtual computing devices, such as devices within acommunication network control plane, devices operating in the dataplane, or a combination thereof. Computing devices used to implementmethod operations may include a processor operatively coupled to memory,the memory providing instructions for execution by the processor toperform the method as described herein.

Computing devices may utilize, at a hardware level, a set of one or moremicroprocessors operatively coupled to a corresponding set of memorycomponents which include stored program instructions for execution bythe microprocessors. Computing devices may be used to provide virtualcomputing resources at one or more levels of virtualization. Forexample, one or more given generic computer hardware platforms may beused to provide one or more virtual computing machines. Computingdevices, such as processor resources, memory, and the like, may also bevirtualized in order to provide resources from which further virtualcomputing machines are built. A set of computing devices which areallocatable for providing various computing resources which in turn areused to realize various computing components of a system, may beregarded as providing a distributed computing system, the internalarchitecture of which may be configured in various ways.

Through the descriptions of the preceding embodiments, the presentinvention may be implemented by using hardware only or by using softwareand a necessary universal hardware platform. Based on suchunderstandings, the technical solution of the present invention may beembodied in the form of a software product. The software product may bestored in a non-volatile or non-transitory storage medium, which can bea compact disk read-only memory (CD-ROM), USB flash disk, or a removablehard disk. The software product includes a number of instructions thatenable a computer device (personal computer, server, or network device)to execute the methods provided in the embodiments of the presentinvention. For example, such an execution may correspond to a simulationof the logical operations as described herein. The software product mayadditionally or alternatively include number of instructions that enablea computer device to execute operations for configuring or programming adigital logic apparatus in accordance with embodiments of the presentinvention.

Although the present invention has been described with reference tospecific features and embodiments thereof, it is evident that variousmodifications and combinations can be made thereto without departingfrom the invention. The specification and drawings are, accordingly, tobe regarded simply as an illustration of the invention as defined by theappended claims, and are contemplated to cover any and allmodifications, variations, combinations or equivalents that fall withinthe scope of the present invention.

What is claimed is:
 1. A method for managing a request in acommunication network, the method comprising: receiving the request by aglobal connection and mobility management (G-CMM) function in thecommunication network; determining if the request can be accommodatedusing one of a plurality of pre-existing network slices of thecommunication network; and instantiating a new network slice toaccommodate the request when the request cannot be accommodated usingany of the plurality of pre-existing network slices.
 2. The method ofclaim 1, wherein the request is a customer service request.
 3. Themethod of claim 1, wherein the request is a request to change attachmentstatus of a mobile device.
 4. The method of claim 1, further comprising:measuring one or more performance metrics indicative of performance ofthe plurality of network slices and the new network slice; and scalingat least one of the plurality of network slices and the new networkslice based on the measured one or more performance metrics.
 5. Themethod of claim 1, wherein instantiating the new network slicecomprises: using a traffic engineering function instantiated for thenetwork slice, performing path computations to determine paths andcapacity bounds for links between source nodes and destination nodes ofthe new network slice, wherein packets are transmitted along thedetermined paths; splitting flows along the determined paths using aflow management function instantiated for the network slice; and causingthe determined capacity bounds to be respected.
 6. A method for managinga mobile device attach request in a communication network having aplurality of network slices, the method comprising: instantiating aglobal connection and mobility management (G-CMM) function in thecommunication network, the G-CMM function configured to operate acrossthe plurality of network slices; selecting a network slice from theplurality of network slices with the G-CMM function; and attaching themobile device to the network slice.
 7. The method of claim 6, whereinthe communication network comprises an access node, the mobile device isassociated with the access node, and the G-CMM function determines andattaches the mobile device to the network slice using extendedcapabilities of the access node.
 8. The method of claim 6, furthercomprising: instantiating a local connection management (CM) function inthe network slice; determining a cloud candidate set for the mobiledevice using the local CM function; and communicatively coupling themobile device to the cloud candidate set.
 9. The method of claim 6,wherein the network slice is selected based at least in part on adetermination that the mobile device is in a coverage area of thenetwork slice.
 10. The method of claim 6, further comprising:instantiating a local connection management (CM) function in the networkslice; determining power savings operating parameters for the mobiledevice using the CM function; and operating the mobile device accordingto the power savings operating parameters.
 11. A connection managementapparatus in a communication network having a plurality of networkslices, the apparatus comprising a microprocessor operatively coupled toa network interface and configured, in response to a request to:determine if the request can be accommodated using one of a plurality ofpre-existing network slices of the communication network; andinstantiate a new network slice to accommodate the request when therequest cannot be accommodated using any of the plurality ofpre-existing network slices.
 12. The apparatus of claim 11, wherein therequest is a customer service request.
 13. The apparatus of claim 11,wherein the request is a request to change attachment status of a mobiledevice.
 14. The apparatus of claim 11, the apparatus further configuredto: obtain one or more performance metrics indicative of performance ofthe plurality of network slices and the new network slice; and scale atleast one of: the plurality of network slices; and the new networkslice, based on the measured one or more performance metrics, whereinmeasuring of the one or more performance metrics is performed by aconnection and mobility manager portion of the apparatus instantiated inat least one of the one or more network slices.
 15. The apparatus ofclaim 11, further comprising: a traffic engineering functioninstantiated for the network slice, the traffic engineering functionconfigured to perform path computations to determine paths and capacitybounds for links between source nodes and destination nodes of the newnetwork slice, wherein packets are transmitted along the determinedpaths; and a flow management function instantiated for the networkslice, the flow management function configured to split flows along thedetermined paths using a flow management function instantiated for thenetwork slice.
 16. A connection management apparatus in a communicationnetwork having a plurality of network slices, the apparatus comprising amicroprocessor operatively coupled to a network interface andconfigured, in response to an attach request from a mobile device to:select a network slice from a plurality of network slices; and transmitinstructions, via the network interface to at least one node of thecommunication network, to attach the mobile device to the network slice.17. The apparatus of claim 16, wherein the communication networkcomprises an access node, the mobile device is associated with theaccess node, and the connection management apparatus is integrated withthe access node and determines and attaches the mobile device to theappropriate network slice using extended capabilities of the accessnode.
 18. The apparatus of claim 16, further comprising: a localconnection management (CM) function instantiated in the network slice,the local CM function configured to: determine a cloud candidate set forthe mobile device; and communicatively couple the mobile device to thecloud candidate set.
 19. The apparatus of claim 16, wherein the networkslice is selected based at least in part on a determination by theconnection management apparatus that the mobile device is in a coveragearea of the network slice.
 20. The apparatus of claim 16, furthercomprising a local connection management (CM) function instantiated inthe network slice, the local CM function configured to determine powersavings operating parameters for the mobile device using the CMfunction, wherein the mobile device is operated according to thedetermined power savings operating parameters.